* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote:
> 06.02.2018 11:43, Greg Kurz wrote:
> > On Tue, 6 Feb 2018 10:49:47 +0300
> > Vladimir Sementsov-Ogievskiy wrote:
> >
> > > 06.02.2018 10:26, Greg Kurz wrote:
> > > > If postcopy-ram was set on the source but not on the destination
06.02.2018 11:43, Greg Kurz wrote:
On Tue, 6 Feb 2018 10:49:47 +0300
Vladimir Sementsov-Ogievskiy wrote:
06.02.2018 10:26, Greg Kurz wrote:
If postcopy-ram was set on the source but not on the destination,
migration doesn't occur, the destination prints an error and boots
the guest:
qemu-sys
On Tue, 6 Feb 2018 10:49:47 +0300
Vladimir Sementsov-Ogievskiy wrote:
> 06.02.2018 10:26, Greg Kurz wrote:
> > If postcopy-ram was set on the source but not on the destination,
> > migration doesn't occur, the destination prints an error and boots
> > the guest:
> >
> > qemu-system-ppc64: Expecte
06.02.2018 10:26, Greg Kurz wrote:
If postcopy-ram was set on the source but not on the destination,
migration doesn't occur, the destination prints an error and boots
the guest:
qemu-system-ppc64: Expected vmdescription section, but got 0
We end up with two running instances.
This behaviour w
If postcopy-ram was set on the source but not on the destination,
migration doesn't occur, the destination prints an error and boots
the guest:
qemu-system-ppc64: Expected vmdescription section, but got 0
We end up with two running instances.
This behaviour was introduced in 2.11 by commit 58110
