[PATCH 0/5] QEMU VFIO live migration

[Cornelia Huck]

On Wed, 20 Feb 2019 11:28:46 +0000
"Gonglei (Arei)" <arei.gonglei at huawei.com> wrote:

> > -----Original Message-----
> > From: Dr. David Alan Gilbert [mailto:dgilbert at redhat.com]
> > Sent: Wednesday, February 20, 2019 7:02 PM
> > To: Zhao Yan <yan.y.zhao at intel.com>
> > Cc: cjia at nvidia.com; kvm at vger.kernel.org; aik at ozlabs.ru;
> > Zhengxiao.zx at alibaba-inc.com; shuangtai.tst at alibaba-inc.com;
> > qemu-devel at nongnu.org; kwankhede at nvidia.com; eauger at redhat.com;
> > yi.l.liu at intel.com; eskultet at redhat.com; ziye.yang at intel.com;
> > mlevitsk at redhat.com; pasic at linux.ibm.com; Gonglei (Arei)
> > <arei.gonglei at huawei.com>; felipe at nutanix.com; Ken.Xue at amd.com;
> > kevin.tian at intel.com; alex.williamson at redhat.com;
> > intel-gvt-dev at lists.freedesktop.org; changpeng.liu at intel.com;
> > cohuck at redhat.com; zhi.a.wang at intel.com; jonathan.davies at nutanix.com
> > Subject: Re: [PATCH 0/5] QEMU VFIO live migration
> > 
> > * Zhao Yan (yan.y.zhao at intel.com) wrote:  
> > > On Tue, Feb 19, 2019 at 11:32:13AM +0000, Dr. David Alan Gilbert wrote:  
> > > > * Yan Zhao (yan.y.zhao at intel.com) wrote:  
> > > > > This patchset enables VFIO devices to have live migration capability.
> > > > > Currently it does not support post-copy phase.
> > > > >
> > > > > It follows Alex's comments on last version of VFIO live migration patches,
> > > > > including device states, VFIO device state region layout, dirty bitmap's
> > > > > query.  

> > > >   b) How do we detect if we're migrating from/to the wrong device or
> > > > version of device?  Or say to a device with older firmware or perhaps
> > > > a device that has less device memory ?  
> > > Actually it's still an open for VFIO migration. Need to think about
> > > whether it's better to check that in libvirt or qemu (like a device magic
> > > along with verion ?).  
> 
> We must keep the hardware generation is the same with one POD of public cloud
> providers. But we still think about the live migration between from the the lower
> generation of hardware migrated to the higher generation.

Agreed, lower->higher is the one direction that might make sense to
support.

But regardless of that, I think we need to make sure that incompatible
devices/versions fail directly instead of failing in a subtle, hard to
debug way. Might be useful to do some initial sanity checks in libvirt
as well.

How easy is it to obtain that information in a form that can be
consumed by higher layers? Can we find out the device type at least?
What about some kind of revision?