Re: VFIO Migration

On Tue, Nov 03, 2020 at 10:13:05AM -0700, Alex Williamson wrote: > On Tue, 3 Nov 2020 11:03:24 + > Stefan Hajnoczi wrote: <...> > > > Management tools need to match the device model/configuration from the > > source device against the destination device. If the destination is > > capable of

Re: VFIO Migration

* Michael S. Tsirkin (m...@redhat.com) wrote: > On Thu, Nov 05, 2020 at 12:13:24PM +, Dr. David Alan Gilbert wrote: > > * Stefan Hajnoczi (stefa...@redhat.com) wrote: > > > On Wed, Nov 04, 2020 at 05:32:02PM +, Dr. David Alan Gilbert wrote: > > > > * Stefan Hajnoczi (stefa...@redhat.com) wr

Re: VFIO Migration

On Thu, Nov 05, 2020 at 11:40:37AM +, Stefan Hajnoczi wrote: > On Wed, Nov 04, 2020 at 05:32:02PM +, Dr. David Alan Gilbert wrote: > > * Stefan Hajnoczi (stefa...@redhat.com) wrote: > > > Michael replied in another sub-thread wondering if versions are really > > > necessary since tools do t

Re: VFIO Migration

On Thu, Nov 05, 2020 at 12:13:24PM +, Dr. David Alan Gilbert wrote: > * Stefan Hajnoczi (stefa...@redhat.com) wrote: > > On Wed, Nov 04, 2020 at 05:32:02PM +, Dr. David Alan Gilbert wrote: > > > * Stefan Hajnoczi (stefa...@redhat.com) wrote: > > > > Michael replied in another sub-thread won

Re: VFIO Migration

* Stefan Hajnoczi (stefa...@redhat.com) wrote: > On Wed, Nov 04, 2020 at 05:32:02PM +, Dr. David Alan Gilbert wrote: > > * Stefan Hajnoczi (stefa...@redhat.com) wrote: > > > Michael replied in another sub-thread wondering if versions are really > > > necessary since tools do the migration check

Re: VFIO Migration

On Thu, Nov 05, 2020 at 07:47:24AM +0100, Gerd Hoffmann wrote: > > > > Yes. If you are creating a custom device that no one else needs to > > > > emulate then you can simply pick a unique URL: > > > > > > > > https://vendor.com/my-dev > > > > > > > > There doesn't need to be anything at the URL

Re: VFIO Migration

On Wed, Nov 04, 2020 at 05:32:02PM +, Dr. David Alan Gilbert wrote: > * Stefan Hajnoczi (stefa...@redhat.com) wrote: > > Michael replied in another sub-thread wondering if versions are really > > necessary since tools do the migration checks. Let's try dropping > > versions to simplify things.

Re: VFIO Migration

Hi, > > > Yes. If you are creating a custom device that no one else needs to > > > emulate then you can simply pick a unique URL: > > > > > > https://vendor.com/my-dev > > > > > > There doesn't need to be anything at the URL. It's just a unique string > > > that no one else will use and ther

Re: VFIO Migration

* Stefan Hajnoczi (stefa...@redhat.com) wrote: > On Wed, Nov 04, 2020 at 10:14:23AM +, Dr. David Alan Gilbert wrote: > > * Stefan Hajnoczi (stefa...@redhat.com) wrote: > > > On Tue, Nov 03, 2020 at 06:49:51PM +, Dr. David Alan Gilbert wrote: > > > > * Stefan Hajnoczi (stefa...@redhat.com) w

Re: VFIO Migration

On Wed, Nov 04, 2020 at 09:07:45AM +0100, Gerd Hoffmann wrote: > > > > The hardware interface together with the device state representation is > > > > called > > > > a *device model*. Device models can be assigned URIs such as > > > > https://qemu.org/devices/e1000e to uniquely identify them. > >

Re: VFIO Migration

On Wed, Nov 04, 2020 at 10:14:23AM +, Dr. David Alan Gilbert wrote: > * Stefan Hajnoczi (stefa...@redhat.com) wrote: > > On Tue, Nov 03, 2020 at 06:49:51PM +, Dr. David Alan Gilbert wrote: > > > * Stefan Hajnoczi (stefa...@redhat.com) wrote: > > > > On Tue, Nov 03, 2020 at 12:17:09PM +,

Re: VFIO Migration

On Wed, Nov 04, 2020 at 02:50:58AM -0500, Michael S. Tsirkin wrote: > On Mon, Nov 02, 2020 at 11:11:53AM +, Stefan Hajnoczi wrote: > > Device States > > - > > The details of the device state representation are not covered in this > > document > > but the general requirements are di

Re: VFIO Migration

On Tue, Nov 03, 2020 at 10:31:35AM -0700, Alex Williamson wrote: > On Tue, 3 Nov 2020 15:33:56 + > Daniel P. Berrangé wrote: > > > On Tue, Nov 03, 2020 at 04:23:43PM +0100, Christophe de Dinechin wrote: > > > > > > On 2020-11-02 at 12:11 CET, Stefan Hajnoczi wrote... > > > > There is discu

Re: VFIO Migration

On Tue, Nov 03, 2020 at 04:23:43PM +0100, Christophe de Dinechin wrote: > On 2020-11-02 at 12:11 CET, Stefan Hajnoczi wrote... > > There is discussion about VFIO migration in the "Re: Out-of-Process > > Device Emulation session at KVM Forum 2020" thread. The current status > > is that Kirti propose

Re: VFIO Migration

> On 3 Nov 2020, at 19:49, Dr. David Alan Gilbert wrote: > > * Stefan Hajnoczi (stefa...@redhat.com ) wrote: >> On Tue, Nov 03, 2020 at 12:17:09PM +, Dr. David Alan Gilbert wrote: >>> * Stefan Hajnoczi (stefa...@redhat.com) wrote: Device Models

Re: VFIO Migration

* Stefan Hajnoczi (stefa...@redhat.com) wrote: > On Tue, Nov 03, 2020 at 06:49:51PM +, Dr. David Alan Gilbert wrote: > > * Stefan Hajnoczi (stefa...@redhat.com) wrote: > > > On Tue, Nov 03, 2020 at 12:17:09PM +, Dr. David Alan Gilbert wrote: > > > > * Stefan Hajnoczi (stefa...@redhat.com) w

Re: VFIO Migration

Hi, > > > The hardware interface together with the device state representation is > > > called > > > a *device model*. Device models can be assigned URIs such as > > > https://qemu.org/devices/e1000e to uniquely identify them. > > > > Is that something that needs to be put together for every d

Re: VFIO Migration

On Mon, Nov 02, 2020 at 11:11:53AM +, Stefan Hajnoczi wrote: > Device States > - > The details of the device state representation are not covered in this > document > but the general requirements are discussed here. > > The device state consists of data accessible through the devi

Re: VFIO Migration

On Tue, Nov 03, 2020 at 06:49:51PM +, Dr. David Alan Gilbert wrote: > * Stefan Hajnoczi (stefa...@redhat.com) wrote: > > On Tue, Nov 03, 2020 at 12:17:09PM +, Dr. David Alan Gilbert wrote: > > > * Stefan Hajnoczi (stefa...@redhat.com) wrote: > > > > Device Models > > > > - > > >

Re: VFIO Migration

On Wed, Nov 04, 2020 at 11:32:34AM +0800, Jason Wang wrote: > > On 2020/11/3 下午8:15, Stefan Hajnoczi wrote: > > On Tue, Nov 03, 2020 at 04:46:53PM +0800, Jason Wang wrote: > > > On 2020/11/2 下午7:11, Stefan Hajnoczi wrote: > > > > There is discussion about VFIO migration in the "Re: Out-of-Process

Re: VFIO Migration

On 2020/11/3 下午8:15, Stefan Hajnoczi wrote: On Tue, Nov 03, 2020 at 04:46:53PM +0800, Jason Wang wrote: On 2020/11/2 下午7:11, Stefan Hajnoczi wrote: There is discussion about VFIO migration in the "Re: Out-of-Process Device Emulation session at KVM Forum 2020" thread. The current status is tha

Re: VFIO Migration

* Stefan Hajnoczi (stefa...@redhat.com) wrote: > On Tue, Nov 03, 2020 at 12:17:09PM +, Dr. David Alan Gilbert wrote: > > * Stefan Hajnoczi (stefa...@redhat.com) wrote: > > > Device Models > > > - > > > Devices have a *hardware interface* consisting of hardware registers, > > > inter

Re: VFIO Migration

On Tue, Nov 03, 2020 at 03:23:03PM +, Daniel P. Berrangé wrote: > On Tue, Nov 03, 2020 at 03:05:08PM +, Stefan Hajnoczi wrote: > > On Tue, Nov 03, 2020 at 11:39:29AM +, Daniel P. Berrangé wrote: > > > On Mon, Nov 02, 2020 at 11:11:53AM +, Stefan Hajnoczi wrote: > > > > Overview > >

Re: VFIO Migration

On Tue, Nov 03, 2020 at 10:13:05AM -0700, Alex Williamson wrote: > On Tue, 3 Nov 2020 11:03:24 + > Stefan Hajnoczi wrote: > > > On Mon, Nov 02, 2020 at 12:38:23PM -0700, Alex Williamson wrote: > > > > > > Cc+ Intel folks as this really bumps into the migration compatibility > > > discussion[

Re: VFIO Migration

On Tue, 3 Nov 2020 15:33:56 + Daniel P. Berrangé wrote: > On Tue, Nov 03, 2020 at 04:23:43PM +0100, Christophe de Dinechin wrote: > > > > On 2020-11-02 at 12:11 CET, Stefan Hajnoczi wrote... > > > There is discussion about VFIO migration in the "Re: Out-of-Process > > > Device Emulation se

Re: VFIO Migration

On Tue, 3 Nov 2020 11:03:24 + Stefan Hajnoczi wrote: > On Mon, Nov 02, 2020 at 12:38:23PM -0700, Alex Williamson wrote: > > > > Cc+ Intel folks as this really bumps into the migration compatibility > > discussion[1][2][3] > > > > On Mon, 2 Nov 2020 11:11:53 + > > Stefan Hajnoczi wrote:

Re: VFIO Migration

On Tue, Nov 03, 2020 at 04:23:43PM +0100, Christophe de Dinechin wrote: > > On 2020-11-02 at 12:11 CET, Stefan Hajnoczi wrote... > > There is discussion about VFIO migration in the "Re: Out-of-Process > > Device Emulation session at KVM Forum 2020" thread. The current status > > is that Kirti prop

Re: VFIO Migration

On Tue, Nov 03, 2020 at 12:17:09PM +, Dr. David Alan Gilbert wrote: > * Stefan Hajnoczi (stefa...@redhat.com) wrote: > > Device Models > > - > > Devices have a *hardware interface* consisting of hardware registers, > > interrupts, and so on. > > > > The hardware interface together

Re: VFIO Migration

On 2020-11-02 at 12:11 CET, Stefan Hajnoczi wrote... > There is discussion about VFIO migration in the "Re: Out-of-Process > Device Emulation session at KVM Forum 2020" thread. The current status > is that Kirti proposed a VFIO device region type for saving and loading > device state. There is cu

Re: VFIO Migration

On Tue, Nov 03, 2020 at 03:05:08PM +, Stefan Hajnoczi wrote: > On Tue, Nov 03, 2020 at 11:39:29AM +, Daniel P. Berrangé wrote: > > On Mon, Nov 02, 2020 at 11:11:53AM +, Stefan Hajnoczi wrote: > > > Overview > > > > > > The purpose of device states is to save the device at a poi

Re: VFIO Migration

On Tue, Nov 03, 2020 at 11:39:29AM +, Daniel P. Berrangé wrote: > On Mon, Nov 02, 2020 at 11:11:53AM +, Stefan Hajnoczi wrote: > > Overview > > > > The purpose of device states is to save the device at a point in time and > > then > > restore the device back to the saved state lat

Re: VFIO Migration

On Tue, Nov 03, 2020 at 04:46:53PM +0800, Jason Wang wrote: > > On 2020/11/2 下午7:11, Stefan Hajnoczi wrote: > > There is discussion about VFIO migration in the "Re: Out-of-Process > > Device Emulation session at KVM Forum 2020" thread. The current status > > is that Kirti proposed a VFIO device re

Re: VFIO Migration

* Stefan Hajnoczi (stefa...@redhat.com) wrote: > There is discussion about VFIO migration in the "Re: Out-of-Process > Device Emulation session at KVM Forum 2020" thread. The current status > is that Kirti proposed a VFIO device region type for saving and loading > device state. There is currently

Re: VFIO Migration

On Mon, Nov 02, 2020 at 11:11:53AM +, Stefan Hajnoczi wrote: > There is discussion about VFIO migration in the "Re: Out-of-Process > Device Emulation session at KVM Forum 2020" thread. The current status > is that Kirti proposed a VFIO device region type for saving and loading > device state. T

Re: VFIO Migration

On Mon, Nov 02, 2020 at 12:38:23PM -0700, Alex Williamson wrote: > > Cc+ Intel folks as this really bumps into the migration compatibility > discussion[1][2][3] > > On Mon, 2 Nov 2020 11:11:53 + > Stefan Hajnoczi wrote: > > > There is discussion about VFIO migration in the "Re: Out-of-Proce

Re: VFIO Migration

On 2020/11/2 下午7:11, Stefan Hajnoczi wrote: There is discussion about VFIO migration in the "Re: Out-of-Process Device Emulation session at KVM Forum 2020" thread. The current status is that Kirti proposed a VFIO device region type for saving and loading device state. There is currently no guid

Re: VFIO Migration

Cc+ Intel folks as this really bumps into the migration compatibility discussion[1][2][3] On Mon, 2 Nov 2020 11:11:53 + Stefan Hajnoczi wrote: > There is discussion about VFIO migration in the "Re: Out-of-Process > Device Emulation session at KVM Forum 2020" thread. The current status > is

Re: VFIO Migration

On Mon, Nov 02, 2020 at 01:28:44PM +0100, Cornelia Huck wrote: > On Mon, 2 Nov 2020 11:11:53 + > Stefan Hajnoczi wrote: > > VFIO Migration > > == > > This document describes how to save and load VFIO device states. Saving a > > device state produces a snapshot of a VFIO device's st

Re: VFIO Migration

On Mon, 2 Nov 2020 11:11:53 + Stefan Hajnoczi wrote: > There is discussion about VFIO migration in the "Re: Out-of-Process > Device Emulation session at KVM Forum 2020" thread. The current status > is that Kirti proposed a VFIO device region type for saving and loading > device state. There i