On Wed, Jul 06, 2016 at 02:29:18PM +0530, Bharata B Rao wrote:
> Add CPUState::migration_id and use that as instance_id in
> vmstate_register() call.
>
> Introduce use-migration-id property that allows target machines to
> optionally switch to using migration_id instead of cpu_index.
> This will h
On Wed, 6 Jul 2016 19:48:03 +0530
Bharata B Rao wrote:
> On Wed, Jul 06, 2016 at 01:34:59PM +0200, Igor Mammedov wrote:
> > On Wed, 6 Jul 2016 14:29:18 +0530
> > Bharata B Rao wrote:
> >
> > > Add CPUState::migration_id and use that as instance_id in
> > > vmstate_register() call.
> > >
> > >
On Wed, Jul 06, 2016 at 01:34:59PM +0200, Igor Mammedov wrote:
> On Wed, 6 Jul 2016 14:29:18 +0530
> Bharata B Rao wrote:
>
> > Add CPUState::migration_id and use that as instance_id in
> > vmstate_register() call.
> >
> > Introduce use-migration-id property that allows target machines to
> > o
On Wed, 6 Jul 2016 14:29:18 +0530
Bharata B Rao wrote:
> Add CPUState::migration_id and use that as instance_id in
> vmstate_register() call.
>
> Introduce use-migration-id property that allows target machines to
> optionally switch to using migration_id instead of cpu_index.
> This will help a
Add CPUState::migration_id and use that as instance_id in
vmstate_register() call.
Introduce use-migration-id property that allows target machines to
optionally switch to using migration_id instead of cpu_index.
This will help allow successful migration in cases where holes are
introduced in cpu_i
