On 30.10.2014 20:00, Ben Hutchings wrote:
[...]
Yes, I can see how this (disabling virtio features) would prevent live
migration from old to new host kernels. You will probably need a
one-time reboot of the guest when migrating to the new host kernel.
We could either mention this in the DSA text, or keep UFO enabled even
though it doesn't work correctly (in practice, we sort of have to do
that as the tap device's feature flags aren't respected by guests -
which I think is a QEMU bug).
Please let us know whether live migration between two hosts running the
new kernel version does work (I think it will).
I confirm that.
Although I did not exactly test this because of some constraints. I
tested with virsh save/restore which uses the same codepaths as virsh
migrate I think. This "cold migration" spewed out the same error
messages as written earlier when migrating from old to new. And it went
fine from new to new.
BTW I use a patched qemu-kvm because of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724758. So maybe there
are only a few wheezy users doing live migrations.
Cheers
Harry
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
