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

2009-11-24 Thread Michael S. Tsirkin
On Mon, Nov 23, 2009 at 08:53:54AM -0600, Anthony Liguori wrote: > Eduardo Habkost wrote: > Migration needs to be conservative. There should be only two possible > outcomes: 1) a successful live migration or 2) graceful failure with the > source VM still running correctly. Silently igno

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

2009-11-24 Thread Michael S. Tsirkin
On Mon, Nov 23, 2009 at 09:12:15AM -0600, Anthony Liguori wrote: > Eduardo Habkost wrote: >> The pvclock MSRs are an example: if the guest is not using pvclock, not >> restoring the MSRs won't make any difference. Strictly speaking, not >> migrating them is wrong, but the user may argue that they k

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

2009-11-24 Thread Paul Brook
> But it's easy to support migration to old qemu just > by discarding the INTx state, and this is not > at all harder, or worse, than migrating from old qemu > to new one. Do we really care about migrating to older versions? Migrating to a new version (backward compatibility) I see the use, it al

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

2009-11-24 Thread Michael S. Tsirkin
On Sun, Nov 22, 2009 at 08:17:46PM -0600, Anthony Liguori wrote: > Paolo Bonzini wrote: >> >>> I don't see how this fixes anything. If you used feature bits, how do >>> you migrate from a version that has a feature bit that an older version >>> doesn't know about? Do you just ignore it? >> >> I'd g