MAAS 3.6: Anyone have success using the MAAS UI for a RHEL 9 virsh KVM Host?

I have a bare-metal server that I want to use as a KVM host. I was able to deploy a custom RHEL 9.6 image (based almost exactly off of this - packer-maas/rhel9 at main · canonical/packer-maas · GitHub), and in my cloud-init user-data install the virtualization packages (see below). I then manually added the machine as a virsh KVM host. When I try and compose a VM, I get the following error -
Pod unable to compose machine: Unable to compose machine because: Failed talking to pod: Virsh command [‘define’, ‘/tmp/tmps_frvhfz’] failed: Failed to define domain from /tmp/tmps_frvhfz error: unsupported configuration: spice graphics are not supported with this QEMU. I know that RHEL 9 doesn’t support spice graphics, is this something that MAAS is specifying in the underlying virt-install command it executes and/or does anyone know why I am getting this error?

Thanks!

#cloud-config
package_update: true
packages:

  • qemu-kvm
  • libvirt
  • virt-install
  • virt-viewer

runcmd:

  • systemctl enable --now libvirtd.socket
  • systemctl enable --now virtlockd.socket
  • systemctl enable --now virtlogd.socket
  • virt-host-validate

Hi @bardeaux307

Indeed, MAAS specifies the the use of spice graphics for virsh: maas/src/provisioningserver/drivers/pod/virsh.py at master · canonical/maas · GitHub

Could you open a bug reporting this issue?

Sure thing - Bug #2121071 “Unable to Compose VM on RHEL 9 virsh KVM Host” : Bugs : MAAS

1 Like