[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Re: Live migration protocol, device features, ABIs and othe

From: Michael S. Tsirkin
Subject: [Qemu-devel] Re: Live migration protocol, device features, ABIs and other beasts
Date: Tue, 24 Nov 2009 15:59:06 +0200
User-agent: Mutt/1.5.19 (2009-01-05)

On Mon, Nov 23, 2009 at 01:15:01PM +0100, Juan Quintela wrote:
> 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).

The way you save state is fundamentally different from what you have in
the machine.  It's easy to imagine where you migrate qemu-1.0 to
qemu-2.0 to qemu-3.0. There's no reason I can see to use 1.0 format in
the second step in the process, and not requiring it will
make it easier for us to get rid of old format support in
the future.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]