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

["Michael S. Tsirkin" <mst@redhat.com>]

On Mon, Nov 23, 2009 at 02:36:40PM +0200, Gleb Natapov wrote:
> > My problem implementing optional features/sections/... is not the
> > savevm/VMState bits.  At the end, implementing that is easy.  What is
> > more dificult is once that a device have 5 features, what are the valid
> > combinations.  i.e. if you have pci and msix features, msix requires
> > pci.  In this case, the dependency is trivial, but in others that
> > hasen't to be so obvious.
> It doesn't matter what device support and how it is configured. This can
> be handled by each device separately. i.e if destination detects that
> source had MSIX enabled for the device but destination hasn't it will
> signal an error.

Yes, this can't work.
But the reverse can: if source does not have MSIX capability
and destination does have it, you can remove MSIX in destination
and make user happy.
One way to do this would be to use the same machine desription
on both sides.

-- 
MST