On Tue, Mar 10, 2015 at 12:28:40AM +0100, Thorsten Glaser wrote:
> On Mon, 9 Mar 2015, Guido Günther wrote:
>
> > wrapping qemu/kvm by a skript or something?
>
> Yes, necessarily:
>
> tglase@tglase:~ $ virsh -c qemu:///system dumpxml MirBSD | fgrep emul
>
> <emulator>/usr/local/bin/qemu-in-chroot</emulator>
> tglase@tglase:~ $ cat /usr/local/bin/qemu-in-chroot
> #!/bin/sh
> exec schroot -c sid-amd64 -u root -- qemu-system-x86_64 -enable-kvm "$@"
>
> Otherwise I cannot assign more than 2047 MiB RAM.
>
> *But*:
>
> tglase@tglase:~ $ virsh -c qemu:///system dumpxml SuSE_Linux_1.0 | fgrep emul
> <emulator>/usr/bin/kvm</emulator>
> tglase@tglase:~ $ virsh -c qemu:///system start SuSE_Linux_1.0
> error: Failed to start domain SuSE_Linux_1.0
> error: unsupported configuration: QEMU 2.1.2 is too new for help parsing
>
> So this also happens for VMs created by virt-manager and
> then untouched.
Please do a:
grep usedQMP /var/cache/libvirt/qemu/capabilities/*.xml
if it doesn't find any matches do a
rm /var/cache/libvirt/qemu/capabilities/*.xml
something seems to be wrong with your capabilities parsing of
qemu. Also it would help to rund libvitd with debug level when
starting the domain and see the output.
>
> > Does
> >
> > virsh capabilities
> >
> > show the same error?
>
> No, it shows a bunch of XML things (capabilities/{host,guest}/…).
Good.
-- Guido
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
