qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH 0/3] Introduce a new --only-migratable option


From: Dr. David Alan Gilbert
Subject: Re: [Qemu-devel] [PATCH 0/3] Introduce a new --only-migratable option
Date: Thu, 15 Dec 2016 19:39:32 +0000
User-agent: Mutt/1.7.1 (2016-10-04)

* Peter Maydell (address@hidden) wrote:
> On 15 December 2016 at 19:03, Dr. David Alan Gilbert
> <address@hidden> wrote:
> > One thing we'd have to do if we did that would be to
> > add another flag to devices to declare that they might
> > sometime in the future call the migrate_add_blocker.
> 
> ...do you have a third-party library to suggest for
> the "foretell the future" functionality necessary
> for devices to implement this correctly? :-)

No, but it'll be available shortly.....

No, what I mean is there are actually three classes of devices:

    a) Devices that are always migratable
    b) Devices that are never migratable (i.e. set the flag in their
       device structure)
    c) Devices that dont have the flag set but sometimes
       based on the action of the guest call migrate_add_blocker.

If you wanted to make it introspectable in this way then you'd
have to add another flag to the device state so that (c) type
devices could be spotted in the introsepction - although
there's no good way to describe well if it's going to be unmigratable
most of the time (e.g. a 9pfs device that's mounted) or only
doing something odd.

Dave

> thanks
> -- PMM
--
Dr. David Alan Gilbert / address@hidden / Manchester, UK



reply via email to

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