You are not logged in.
Hi,
After a reboot due to unrelated issues, virt-manager is not showing any of the VMs I had configured via qemu:
I checked connection properties, and everything else is showing up correctly, like the networks and storage. I tried to create new VMs out of existing storage and got this message:
Googling it suggested this happens when KVM module is not loaded. I modprobed kvm, kvm_intel and still got same result.
Systemd gave me the following:
% systemctl status libvirtd
libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)
Active: active (running) since Sat 2013-06-08 08:55:19 IST; 29min ago
Main PID: 1499 (libvirtd)
CGroup: name=systemd:/system/libvirtd.service
├─ 834 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf
├─ 863 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/nat_static.conf
├─ 881 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/closed_dhcp.conf
└─1499 /usr/bin/libvirtd -p /var/run/libvirtd.pid
Jun 08 09:07:48 core libvirtd[1499]: internal error Cannot find suitable emulator for x86_64
Jun 08 09:07:48 core libvirtd[1499]: internal error Cannot find suitable emulator for x86_64
Jun 08 09:07:48 core libvirtd[1499]: internal error Cannot find suitable emulator for x86_64
Jun 08 09:07:48 core libvirtd[1499]: internal error Cannot find suitable emulator for x86_64
Jun 08 09:07:48 core libvirtd[1499]: internal error Cannot find suitable emulator for x86_64
Jun 08 09:07:48 core libvirtd[1499]: internal error Cannot find suitable emulator for x86_64
Jun 08 09:08:20 core libvirtd[1499]: internal error Cannot find suitable emulator for x86_64
Jun 08 09:08:20 core libvirtd[1499]: internal error Cannot find suitable emulator for x86_64
Jun 08 09:08:35 core libvirtd[1499]: internal error Cannot find suitable emulator for x86_64
Jun 08 09:08:35 core libvirtd[1499]: internal error Cannot find suitable emulator for x86_64
Googling that seems to indicate that this happens when virtualization is disabled by BIOS. But cpuinfo tells me that vm is supported:
% grep vmx /proc/cpuinfo | uniq -c
8 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid
Can anyone help me? Has anyone else faced a similar problem?
Here are some version info:
local/libvirt 1.0.6-1
API for controlling virtualization engines (openvz,kvm,qemu,virtualbox,xen,etc)
local/qemu 1.4.2-1
A generic and open source processor emulator which achieves a good emulation speed by using dynamic translation.
Of which, qemu got updated just today. I will try rolling back to older version and post and update.
Ninja edit: Looks to be qemu. Just running qemu gives me this error:
% qemu-system-x86_64
qemu-system-x86_64: error while loading shared libraries: libiscsi.so.1: cannot open shared object file: No such file or directory
EDIT: The resolution was
pacman -S libiscsi libaio
systemctl restart libvirtd
EDIT2: Made subject line better searchable
Last edited by railmaniac (2013-06-08 04:19:24)
Thanks,
railmaniac
Offline
Ok, I tried downgrading qemu, but no I'm getting this error:
% sudo pacman -U /var/cache/pacman/pkg/qemu-1.4.1-3-x86_64.pkg.tar.xz
loading packages...
warning: downgrading package qemu (1.4.2-1 => 1.4.1-3)
resolving dependencies...
looking for inter-conflicts...
:: bluez and obexd-client are in conflict. Remove obexd-client? [y/N] y
:: bluez and bluez4 are in conflict. Remove bluez4? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: bluedevil: requires obexd-client
:: libbluedevil: requires bluez4
Thanks,
railmaniac
Offline
I tried going the other way and install libiscsi. Then I got an error for libaio - installed that as well and qemu was able to launhc on its own.
Once I restarted libvirtd it was working correctly. I'm marking this as resolved - should I open a bug under qemu?
Thanks,
railmaniac
Offline
OK, looks like there already a couple of bugs for this:
Thanks,
railmaniac
Offline
HI,
First of all thanks a lot for this post. I am facing the same issue since yest.
After reboot, my VMs gone missing and even virt-manager was not working (as shown in the screenshots which you have pasted in your post).
Now after trying out the workout which you had mentioned, I am able to get the virt-manager working.
But I am not sure if I can get back my missing VMs .
I am new to linux. Kindly guide me on how I can get back those VMs.
[root@skoduri lib64]# ls /etc/libvirt/qemu/
networks rhel6-vm2.xml rhel6.xml
[root@skoduri lib64]#
[root@skoduri lib64]# ls /etc/libvirt/storage/
autostart default.xml storage_1.xml
[root@skoduri lib64]#
[root@skoduri lib64]#
Thanks,
Soumya
Offline