Can't create VM using virt-manager

tomocafe

When opening virt-manager and pressing the new VM button, I get the error dialog "Error: host does not support any virtualization options".

Here are the contents of the virt-manager log ~/.cache/virt-manager/virt-manager.log:

https://hastebin.com/oxubajefex.xml

Of note:

[Sun, 31 Mar 2019 09:10:03 virt-manager 20062] DEBUG (connection:321) Error calling getVersion
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtinst/connection.py", line 319, in conn_version
    self._conn_version = self._libvirtconn.getVersion()
  File "/usr/lib/python3.6/site-packages/libvirt.py", line 3992, in getVersion
    if ret == -1: raise libvirtError ('virConnectGetVersion() failed', conn=self)
libvirt.libvirtError: internal error: Cannot find suitable emulator for x86_64

A quick Google search shows at least another person with the same issue recently: https://www.reddit.com/r/kvm/comments/b4w1t0/no_virtualization_options_solus

The log file shows the HW information from virsh capabilities. But in case it helps:

$ inxi -F
System:    Host: u410 Kernel: 4.20.16-112.current x86_64 bits: 64 Desktop: Budgie 10.5 Distro: Solus 4.0 
Machine:   Type: Laptop System: LENOVO product: IdeaPad U410 v: Lenovo U410 serial: <root required> 
           Mobo: LENOVO model: Lenovo v: Lenovo U410 serial: <root required> UEFI: LENOVO v: 65CN15WW date: 06/05/2012 
Battery:   ID-1: BAT1 charge: 25.4 Wh condition: 38.7/44.1 Wh (88%) 
CPU:       Topology: Dual Core model: Intel Core i7-3517U bits: 64 type: MT MCP L2 cache: 4096 KiB 
           Speed: 899 MHz min/max: 800/3000 MHz Core speeds (MHz): 1: 813 2: 847 3: 1090 4: 808 
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel 
           Device-2: NVIDIA GF119M [GeForce 610M] driver: nouveau v: kernel 
           Display: x11 server: X.Org 1.20.3 driver: intel,nouveau unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 19.0.0 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k4.20.16-112.current 
Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169 
           IF: enp3s0 state: down mac: 04:7d:7b:ff:1c:16 
           Device-2: Intel Centrino Wireless-N 2200 driver: iwlwifi 
           IF: wlp4s0 state: up mac: 9c:4e:36:32:39:d4 
           IF-ID-1: virbr0 state: down mac: 52:54:00:53:db:ae 
           IF-ID-2: virbr0-nic state: down mac: 52:54:00:53:db:ae 
Drives:    Local Storage: total: 931.51 GiB used: 9.67 GiB (1.0%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000LM024 HN-M101MBB size: 931.51 GiB 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci 
Partition: ID-1: / size: 911.75 GiB used: 9.67 GiB (1.1%) fs: ext4 dev: /dev/dm-1 
           ID-2: swap-1 size: 3.73 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-0 
Sensors:   System Temperatures: cpu: 40.0 C mobo: N/A gpu: nouveau temp: 44 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 225 Uptime: 2d 20h 10m Memory: 7.66 GiB used: 1.36 GiB (17.7%) Shell: bash inxi: 3.0.32

dbarron

Did you enable virtualization in your BIOS?

tomocafe

dbarron Yes, in my BIOS it's called "Intel virtual technology" and it's enabled. I have power cycled (many times) since turning that on. This also used to be a Win7 machine and I was using VirtualBox on it several years ago.

tomocafe

Hmm, it seems libvirtd is running but there are errors. I started it but never checked the status until now. Not sure if these need to be fixed or not.

$ sudo systemctl status libvirtd
● libvirtd.service - Virtualization daemon
   Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-28 14:14:18 PDT; 2 days ago
     Docs: man:libvirtd(8)
           https://libvirt.org
 Main PID: 756 (libvirtd)
    Tasks: 19 (limit: 32768)
   Memory: 24.6M
   CGroup: /system.slice/libvirtd.service
           ├─756 /usr/sbin/libvirtd
           ├─912 /usr/bin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/libvirt_leaseshelper
           └─913 /usr/bin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/libvirt_leaseshelper

Mar 31 09:10:05 u410 libvirtd[756]: 2019-03-31 16:10:05.491+0000: 774: error : virQEMUCapsNewForBinaryInternal:4539 : internal error: Failed to probe QEMU binary with QMP: /usr/bin/qemu-system-aarch64: error while loading shared libraries: libvirglrenderer.so.0: cannot open shared object file: No such file or directory
Mar 31 09:10:05 u410 libvirtd[756]: 2019-03-31 16:10:05.491+0000: 774: warning : virQEMUCapsLogProbeFailure:4486 : Failed to probe capabilities for /usr/bin/qemu-system-aarch64: internal error: Failed to probe QEMU binary with QMP: /usr/bin/qemu-system-aarch64: error while loading shared libraries: libvirglrenderer.so.0: cannot open shared object file: No such file or directory
Mar 31 09:10:05 u410 libvirtd[756]: 2019-03-31 16:10:05.495+0000: 774: error : virQEMUCapsNewForBinaryInternal:4539 : internal error: Failed to probe QEMU binary with QMP: /usr/bin/qemu-system-i386: error while loading shared libraries: libvirglrenderer.so.0: cannot open shared object file: No such file or directory
Mar 31 09:10:05 u410 libvirtd[756]: 2019-03-31 16:10:05.495+0000: 774: warning : virQEMUCapsLogProbeFailure:4486 : Failed to probe capabilities for /usr/bin/qemu-system-i386: internal error: Failed to probe QEMU binary with QMP: /usr/bin/qemu-system-i386: error while loading shared libraries: libvirglrenderer.so.0: cannot open shared object file: No such file or directory
Mar 31 09:10:05 u410 libvirtd[756]: 2019-03-31 16:10:05.500+0000: 774: error : virQEMUCapsNewForBinaryInternal:4539 : internal error: Failed to probe QEMU binary with QMP: /usr/bin/qemu-system-mips: error while loading shared libraries: libvirglrenderer.so.0: cannot open shared object file: No such file or directory
Mar 31 09:10:05 u410 libvirtd[756]: 2019-03-31 16:10:05.500+0000: 774: warning : virQEMUCapsLogProbeFailure:4486 : Failed to probe capabilities for /usr/bin/qemu-system-mips: internal error: Failed to probe QEMU binary with QMP: /usr/bin/qemu-system-mips: error while loading shared libraries: libvirglrenderer.so.0: cannot open shared object file: No such file or directory
Mar 31 09:10:05 u410 libvirtd[756]: 2019-03-31 16:10:05.504+0000: 774: error : virQEMUCapsNewForBinaryInternal:4539 : internal error: Failed to probe QEMU binary with QMP: /usr/bin/qemu-system-mipsel: error while loading shared libraries: libvirglrenderer.so.0: cannot open shared object file: No such file or directory
Mar 31 09:10:05 u410 libvirtd[756]: 2019-03-31 16:10:05.504+0000: 774: warning : virQEMUCapsLogProbeFailure:4486 : Failed to probe capabilities for /usr/bin/qemu-system-mipsel: internal error: Failed to probe QEMU binary with QMP: /usr/bin/qemu-system-mipsel: error while loading shared libraries: libvirglrenderer.so.0: cannot open shared object file: No such file or directory
Mar 31 09:10:05 u410 libvirtd[756]: 2019-03-31 16:10:05.509+0000: 774: error : virQEMUCapsNewForBinaryInternal:4539 : internal error: Failed to probe QEMU binary with QMP: /usr/bin/qemu-system-x86_64: error while loading shared libraries: libvirglrenderer.so.0: cannot open shared object file: No such file or directory
Mar 31 09:10:05 u410 libvirtd[756]: 2019-03-31 16:10:05.509+0000: 774: warning : virQEMUCapsLogProbeFailure:4486 : Failed to probe capabilities for /usr/bin/qemu-system-x86_64: internal error: Failed to probe QEMU binary with QMP: /usr/bin/qemu-system-x86_64: error while loading shared libraries: libvirglrenderer.so.0: cannot open shared object file: No such file or directory

tomocafe

tomocafe I installed packages virglrenderer and spice and it no longer gives me that error. Should these be dependencies of virt-manager or more likely kvm/qemu?

tomocafe

tomocafe Hmm... qemu's package.yml shows virglrenderer and spice-server as dependencies since it's built with --enable-virglrenderer and --enable-spice, but somehow I had qemu installed and not those dependencies.

Justin

Those are build-time dependencies, not run-time.

Christoph3

Justin Hi there, my gnome-boxes without those dependencies dont work either. I had t install them and after do the kyrios suggested to get gnome-boxes working as stated here https://dev.getsol.us/D5955 .

Best regards

clauded

I had the same problem with a fresh install of Solus Plasma. Are you using Budgie?

tomocafe

clauded Yep, Budgie, although I don't think the DE will make a difference here.

DuIslingr

Had the same problem upon installing qemu and trying to setup a vm. Installing virglrenderer and spice packages and restarting libvirtd solved the problem. also had a prior issue with libvirtd not enabling by default and had to enable it manually even after a reboot

kyrios

DuIslingr libvirtd not enabling by default and had to enable it manually even after a reboot

This is the normal behaviour. If you want to service the start automatically at boot you have to use systemctl enable ...

RAM

This is definitely an issue and should be added to dependencies. Spent the last two hours trying to figure out why my VMs were not working. adding virglrenderer and spice and restarting libvirtd worked.

JoshStrobl

This will be fixed in next week's sync. Apologies for the delay. For what it is worth, @Gaming4LifeDE submitted a patch some time ago but I held it back since it would've required GNOME Boxes to be updated, and this was prior to the stack upgrade. So please forward your thanks to them for the fix. I just basically commandeered it.