Re: qemu-kvm (1.0) sqeeeze-backports request to fix libvirt (0.9.8-2) and debian linux-ha clusters
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 17.01.2012 20:07, Jelle de Jong wrote:
> Hello everybody,
>
> I got an important issue that hit my systems today.
>
> I upgraded libvirt on a linux-ha virtualisation cluster and as a result the cluster broke and live migrations stopped working. After investigation it seems the qemu-kvm 0.12.5+dfsg-5+squeeze6 version is buggy and the new libvirt (0.9.8-2~bpo60+2) is using features with are broken in qemu-kvm 0.12.5.
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637990
>
> "#virt 16:58 < danpb> the newer libvirt tries to use some functionality which is broken in your qemu"
>
> Could somebody backport qemu-kvm (1.0+dfsg-3) http://packages.debian.org/wheezy/qemu-kvm It is needed to fix the clusters...
> # virsh migrate --live ... error: internal error unable to send file handle 'migrate': No file descriptor supplied via SCM_RIGHTS
>
> I hope this is important enough to give it high priority?
It is not easy to backport qemu-kvm since it requires
backporting seabios and vgabios (new qemu-kvm does not
work with old *bios) and a few other packages like spice,
rbd/rados, libiscsi and others. While the "other" packages
are just extra features and optional, *bios (and ipxe)
are mandatory, but new versions of *bios will break old
qemu and old qemu-kvm, so whole qemu needs to be backported
at the same time too.
I considered uploading a backport of qemu-kvm to squeeze
several times (I maintain main qemu-kvm package) but it
is still not done due to the above reasons.
The better route will be to fix libvirt to not use
features which are known broken. Just IMHO anyway.
And the highest priority is to mark new libvirt as
Break'ing old qemu[-kvm] properly.
As for the particular bug you mentioned (#637990), I think
I can just fix it for squeeze in 0.12. Not sure if I can
catch the next point release however. And there's one
security fix pending for squeeze release of qemu-kvm, too
but that one is difficult to backport (I tried and even
succeeded but am still not sure I got it right).
Thanks,
/mjt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iJwEAQECAAYFAk8XGAQACgkQUlPFrXTwyDgvRwQAycjg0zWHrLaxwTRoht9W7jpn
Kd5UYck8xyGj1jF7t/MUcrONYvxADu/KRSduaiJf+ByvO6cmY+b0/esQigNgY80q
4neo4PCklQVPPFkLqhMAilnFnWgnkQ1dp0TzydZW7KrF5sAKly4AfAcRM8Bs7rhx
/mZBUzt1GXWakqiXif8=
=Ri8E
-----END PGP SIGNATURE-----
Reply to: