reassign 780093 libvirt-daemon
severity 780093 normal
retitule 780093 Fails capability parsing in a bind mounted amd64 chroot on x32
On Mon, Mar 16, 2015 at 03:43:10PM +0100, Thorsten Glaser wrote:
severity 780093 important
thanks
sigh
On Wed, 11 Mar 2015, Guido Günther wrote:
That said
On Tue, 17 Mar 2015, Guido Günther wrote:
This is a special setup that fails to parse the capabilities using a
qemu wrapper on x32 to run in a x86_64 chroot (as far as I understand
It also fails to parse them *without* the chroot, with…
emulator/usr/bin/kvm/emulator
… which is what
severity 780093 important
thanks
On Wed, 11 Mar 2015, Guido Günther wrote:
That said having the logs and maybe stracing the daemon should
provide more insights.
Did you get any more insights?
In the meantime, I downgraded libvirt0 (and the three dependants
libvirt-clients libvirt-daemon
severity 780093 normal
thanks
On Wed, Mar 11, 2015 at 03:09:11PM +0100, Thorsten Glaser wrote:
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
On Wed, 11 Mar 2015, Guido Günther wrote:
I wonder why you still have capabilities.* sockets. Maybe these are
Nonono, these are happening *during* my tests, in which I removed
the daemonising parameter from the qemu call.
I'm lowering the severity since the issue looks pretty much related to
On Wed, 11 Mar 2015, Guido Günther wrote:
Please do a:
grep usedQMP /var/cache/libvirt/qemu/capabilities/*.xml
root@tglase:~ # grep usedQMP /var/cache/libvirt/qemu/capabilities/*.xml
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
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
On Wed, Mar 11, 2015 at 01:24:48PM +0100, Thorsten Glaser wrote:
[..snip..]
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.
How do I do that? Can’t find anything in the
On Mon, Mar 09, 2015 at 10:05:02AM +0100, Thorsten Glaser wrote:
Package: libvirt-clients
Version: 1.2.9-9
Severity: grave
Justification: renders package unusable
tglase@tglase:~ $ virsh -c qemu:///system start MirBSD
error: Failed to start domain MirBSD
error: unsupported configuration:
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
11 matches
Mail list logo
