# Libvirt / unsupported configuration **URL:** \ **Category:** Rocky Linux Help & Support\ **Tags:** rocky-linux-9\ **Created:** [February 9, 2025, 9:06am UTC](https://forums.rockylinux.org/t/libvirt-unsupported-configuration/17486 "2025-02-09T09:06:09Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![tango](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/tango/32/1150_2.png) [@tango](https://forums.rockylinux.org/u/tango)\ **Post date:** [February 9, 2025, 9:06am UTC](https://forums.rockylinux.org/t/libvirt-unsupported-configuration/17486/1 "2025-02-09T09:06:09Z")
I’m encountering an error message while attempting to create a virtual machine with libvirt libvirt… LibvirtError: unsupported configuration: domain configuration does not support video model ‘virtio’ My kernel is 5.14.0-503.15.1.el9\_5.x86\_64 in Rocky 9.5 ---
**Author:** ![gerry666uk](https://avatars.discourse-cdn.com/v4/letter/g/dbc845/32.png) [@gerry666uk](https://forums.rockylinux.org/u/gerry666uk)\ **Post date:** [February 10, 2025, 10:02pm UTC](https://forums.rockylinux.org/t/libvirt-unsupported-configuration/17486/2 "2025-02-10T22:02:57Z")
Probably best if you show the exact commands you used, and whether you were creating as root or standard user. ---
**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\ **Post date:** [February 11, 2025, 8:24am UTC](https://forums.rockylinux.org/t/libvirt-unsupported-configuration/17486/3 "2025-02-11T08:24:56Z")
Maybe one of these packages needs to be installed? ```auto root@rocky9:~# dnf list qemu* | grep -i virt qemu-kvm-device-display-virtio-gpu.x86_64 17:9.0.0-10.el9_5.2 appstream qemu-kvm-device-display-virtio-gpu-pci.x86_64 17:9.0.0-10.el9_5.2 appstream qemu-kvm-device-display-virtio-vga.x86_64 17:9.0.0-10.el9_5.2 appstream ``` ---
**Author:** ![tango](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/tango/32/1150_2.png) [@tango](https://forums.rockylinux.org/u/tango)\ **Post date:** [February 11, 2025, 8:59am UTC](https://forums.rockylinux.org/t/libvirt-unsupported-configuration/17486/4 "2025-02-11T08:59:27Z")
Hello iwalker Following a thread ( [https://bugs.launchpad.net/nova/+bug/2018172](https://bugs.launchpad.net/nova/+bug/2018172) ), I did **grubby --update-kernel ALL --args intel\_iommu=on** and seems to solve the problem The packages are already installed qemu-kvm-device-display-virtio-gpu-9.0.0-10.el9\_5.2.x86\_64 qemu-kvm-device-display-virtio-gpu-pci-9.0.0-10.el9\_5.2.x86\_64 qemu-kvm-device-display-virtio-vga-9.0.0-10.el9\_5.2.x86\_64 Thank you very much ---
**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\ **Post date:** [February 11, 2025, 10:17am UTC](https://forums.rockylinux.org/t/libvirt-unsupported-configuration/17486/5 "2025-02-11T10:17:14Z")
Strange, on my Rocky 9 I have this: ```auto root@kvm:~# dmesg | grep -i iommu [0.000000] Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.14.0-503.22.1.el9_5.x86_64 root=/dev/mapper/rl_kvm-root ro rd.lvm.lv=rl_kvm/root intel_iommu=on [0.000000] Kernel command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.14.0-503.22.1.el9_5.x86_64 root=/dev/mapper/rl_kvm-root ro rd.lvm.lv=rl_kvm/root intel_iommu=on [0.000000] DMAR: IOMMU enabled ``` but nowhere is it enabled in grub. That said I did do a group install rather than only select certain packages. ---
**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\ **Post date:** [February 11, 2025, 11:55am UTC](https://forums.rockylinux.org/t/libvirt-unsupported-configuration/17486/6 "2025-02-11T11:55:33Z")
I see some Dell servers (Rn40 series) that do not have intel\_iommu=on on the cmdline, yet libvirtd is ok with ‘virtio’. Perhaps Dell BIOS talks with kernel more than others? * * * > [@iwalker](#): > > I did do a group install rather than only select certain packages. Group install, like `dnf group install virtualization-hypervisor` which has only two (mandatory) packages: `libvirt`and `qemu-kvm` The latter pulls in multiple `qemu-kvm-*` packages. Therefore, if the “certain packages” are libvirt and qemu-kvm, then it is practically same as group Virtualization Hypervisor. * * * None of those does, AFAIK, add kernel cmdline options. It is left to the user to know whether they need IOMMU and specifically whether the `intel_iommu=on` is the correct word for their hardware. * * * > [@iwalker](#): > > but nowhere is it enabled in grub. The BLS entries are in `/boot/loader/entries/` by default. That is where the kernelopts are set. The entries get their content from grubby; options from `/etc/kernel/cmdline` The `/etc/defaults/grub` may or may not be in sync. (Ideally, it should be kept in sync.) * * * PS. I was just looking at the “postinstall” scripts of NVidia proprietary RPMs from NVidia’s CUDA repo and from ELRepo. Both do add kernelopts. Both/either do not synchronously update all the spots that could affect kernelopts for the next installed kernel in el9. Its a mess. ---
**Author:** ![tango](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/tango/32/1150_2.png) [@tango](https://forums.rockylinux.org/u/tango)\ **Post date:** [February 11, 2025, 12:06pm UTC](https://forums.rockylinux.org/t/libvirt-unsupported-configuration/17486/7 "2025-02-11T12:06:33Z")
Hi iwalker, I’m using libvirtd from openstack. Normally this one installs all dependency with. That was true in Rocky8, now in Rocky9 I see that you have to make some adjustments. For example libvirtd I had to install it by hand. Plus I also found the latter problem with the virtio driver. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\ **Post date:** [April 12, 2025, 12:06pm UTC](https://forums.rockylinux.org/t/libvirt-unsupported-configuration/17486/8 "2025-04-12T12:06:56Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.