Dor Laor<address@hidden> wrote:
> In the last couple of days we discovered some issues regarding stable
> ABI and the robustness of the live migration protocol. Let's just jump
> right into it, ordered by complexity:
>
> 1. Control*every* feature exposed to the guest by qemu cmdline:
>
> While thinking on cross version migration, and reviewing some
> patches, I noticed that there are many times that we use feature bits
> in order to expose functionality for the guest driver - example:
> VIRTIO_BLK_F_BARRIER, but we do not control it from qemu cmdline.
In my opinion this is madness, qemu command line is already too
complicated. I agree with anthony to put it in the command line.
I will go further, and think that this kind of issues should be put into
the machine type.
If you start qemu with -M pc-0.10, it should save the state in a 0.10
compatible way (that don't happens at the moment, but it should work
that way).