On Wed, Sep 01, 2021 at 01:35:18PM +0200, Markus Armbruster wrote:
> Peter Xu writes:
>
> > Markus,
> >
> > On Wed, Aug 25, 2021 at 09:54:12AM +0200, Markus Armbruster wrote:
> >> Peter Xu writes:
> >>
> >> > Both dump-guest-memory and live migration have vm state cached
> >> > internally.
> >
Peter Xu writes:
> Markus,
>
> On Wed, Aug 25, 2021 at 09:54:12AM +0200, Markus Armbruster wrote:
>> Peter Xu writes:
>>
>> > Both dump-guest-memory and live migration have vm state cached internally.
>> > Allowing them to happen together means the vm state can be messed up.
>> > Simply
>> >
Markus,
On Wed, Aug 25, 2021 at 09:54:12AM +0200, Markus Armbruster wrote:
> Peter Xu writes:
>
> > Both dump-guest-memory and live migration have vm state cached internally.
> > Allowing them to happen together means the vm state can be messed up.
> > Simply
> > block live migration for dump-
Peter Xu writes:
> Both dump-guest-memory and live migration have vm state cached internally.
> Allowing them to happen together means the vm state can be messed up. Simply
> block live migration for dump-guest-memory.
>
> One trivial thing to mention is we should still allow dump-guest-memory e
Both dump-guest-memory and live migration have vm state cached internally.
Allowing them to happen together means the vm state can be messed up. Simply
block live migration for dump-guest-memory.
One trivial thing to mention is we should still allow dump-guest-memory even if
-only-migratable is s
