Re: [Qemu-devel] [PATCH] migration: allow private destination ram with x-ignore-shared

* Dr. David Alan Gilbert (dgilb...@redhat.com) wrote: > * Peng Tao (tao.p...@linux.alibaba.com) wrote: > > By removing the share ram check, qemu is able to migrate > > to private destination ram when x-ignore-shared capability > > is on. Then we can create multiple destination VMs based > > on the

Re: [Qemu-devel] [PATCH] migration: allow private destination ram with x-ignore-shared

* Peng Tao (tao.p...@linux.alibaba.com) wrote: > By removing the share ram check, qemu is able to migrate > to private destination ram when x-ignore-shared capability > is on. Then we can create multiple destination VMs based > on the same source VM. > > This changes the x-ignore-shared migration

Re: [Qemu-devel] [PATCH] migration: allow private destination ram with x-ignore-shared

On 2019/6/14 14:35, Peng Tao wrote: By removing the share ram check, qemu is able to migrate to private destination ram when x-ignore-shared capability is on. Then we can create multiple destination VMs based on the same source VM. This changes the x-ignore-shared migration capability to

[Qemu-devel] [PATCH] migration: allow private destination ram with x-ignore-shared

By removing the share ram check, qemu is able to migrate to private destination ram when x-ignore-shared capability is on. Then we can create multiple destination VMs based on the same source VM. This changes the x-ignore-shared migration capability to work similar to Lai's original