[Pkg-libvirt-maintainers] Bug#780093: Bug#780093: libvirt: error: unsupported configuration: QEMU 2.1.2 is too new for help parsing

[Thorsten Glaser]

On Wed, 11 Mar 2015, Guido Günther wrote:

> qemu. Also it would help to rund libvitd with debug level when
> starting the domain and see the output.

sudo env LIBVIRT_DEBUG=1 /etc/init.d/libvirtd start #, thus.

This is interesting. For the VMs created by virt-manager, which
have /usr/bin/kvm as emulator, it says KVM not supported by this
target. This matches the command line:

tglase at tglase:~ $ kvm
KVM not supported for this target
No accelerator found!

This is probably an x32 issue with src:qemu.

For the VMs using qemu-in-chroot, it instead tries to start it with
-qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait
and then fails to connect there. That being said, /var/lib/libvirt
is already in the list of schroot bind-mount directories, so this
should work. And indeed, if I run…

LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin HOME=/ /usr/local/bin/qemu-in-chroot -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile

… manually, then check the “mount” output, the directory is bindmounted.

tglase at tglase:~ $ sudo ls -l /var/lib/libvirt/qemu/                                                        
total 20
srwxr-xr-x 1 root         root            0 Mär 11 15:05 capabilities.monitor.sock
-rw------- 1 root         root            6 Mär 11 15:05 capabilities.pidfile
drwxr-x--- 3 libvirt-qemu libvirt-qemu 4096 Okt 28 09:17 channel
drwxr-xr-x 2 root         root         4096 Okt 28 09:17 dump
drwxr-xr-x 2 libvirt-qemu libvirt-qemu 4096 Okt 28 09:17 save
drwxr-xr-x 2 libvirt-qemu libvirt-qemu 4096 Okt 28 09:17 snapshot

If I connect to this from outside the chroot, I get:

tglase at tglase:~ $ sudo nc -U /var/lib/libvirt/qemu/capabilities.monitor.sock
{"QMP": {"version": {"qemu": {"micro": 2, "minor": 1, "major": 2}, "package": " (Debian 1:2.1+dfsg-11)"}, "capabilities": []}}

Does this help?

For the record, if I go into a (the same) chroot manually, start qemu
with -qmp, then connect to that inside the same chroot, I get the same
output. The presence or absence of -enable-kvm also does not change it.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg