On Mon, 23 May 2016 21:42:23 +0530
Amit Shah wrote:
> On (Wed) 11 May 2016 [14:10:34], Greg Kurz wrote:
> > On Wed, 11 May 2016 13:59:19 +0200
> > Paolo Bonzini wrote:
> >
> > > On 04/05/2016 21:44, Greg Kurz wrote:
> > > > QEMU has currently two ways to prevent migration to occur:
> > > >
On (Wed) 11 May 2016 [14:10:34], Greg Kurz wrote:
> On Wed, 11 May 2016 13:59:19 +0200
> Paolo Bonzini wrote:
>
> > On 04/05/2016 21:44, Greg Kurz wrote:
> > > QEMU has currently two ways to prevent migration to occur:
> > > - migration blocker when it depends on runtime state
> > > - VMStateDesc
On Wed, 11 May 2016 13:59:19 +0200
Paolo Bonzini wrote:
> On 04/05/2016 21:44, Greg Kurz wrote:
> > QEMU has currently two ways to prevent migration to occur:
> > - migration blocker when it depends on runtime state
> > - VMStateDescription.unmigratable when migration is not supported at all
> >
On 04/05/2016 21:44, Greg Kurz wrote:
> QEMU has currently two ways to prevent migration to occur:
> - migration blocker when it depends on runtime state
> - VMStateDescription.unmigratable when migration is not supported at all
>
> This patch gathers all the logic into a single function to be c
On Wed, 04 May 2016 21:44:19 +0200
Greg Kurz wrote:
> QEMU has currently two ways to prevent migration to occur:
> - migration blocker when it depends on runtime state
> - VMStateDescription.unmigratable when migration is not supported at all
>
> This patch gathers all the logic into a single fu
QEMU has currently two ways to prevent migration to occur:
- migration blocker when it depends on runtime state
- VMStateDescription.unmigratable when migration is not supported at all
This patch gathers all the logic into a single function to be called from
both the savevm and the migrate paths.