[question] cpumap: why 'mpx' removed from Cooperlake model?

Hi, Jiri I just compared the cpu features between the 'x86_Cooperlake.xml ' and 'x86_Cascadelake-Server.xml', the feature 'mpx' seems removed from the Cooperlake model. Is there a reason? And what rules do we follow to add or remove CPU features? Regards, Xin

RE: [PATCH v3 0/2] qemu: support shmem device migration

> On Fri, Jul 24, 2020 at 11:34:10AM +0800, Wang Xin wrote: > >Shmem device support property role with 'master'(master=on) or > >'peer'(master=off, default mode), which controls to copy the shared > >memory on migration to the destination host or not. see >

RE: [PATCH v3 1/2] qemu: add support for shmem-{plain, doorbell} role

> On Mon, Aug 03, 2020 at 09:26:19AM +0000, Wangxin (Alexander) wrote: > >> On Fri, Jul 24, 2020 at 11:34:11AM +0800, Wang Xin wrote: > >> >Role(master or peer) controls how the domain behaves on migration. > >> >For more details about migration with ivshme

RE: [PATCH v3 1/2] qemu: add support for shmem-{plain, doorbell} role

> On Fri, Jul 24, 2020 at 11:34:11AM +0800, Wang Xin wrote: > >Role(master or peer) controls how the domain behaves on migration. > >For more details about migration with ivshmem, see > >https://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/system/ivshmem.rst;hb=HEAD > > > >It's a optional

RE: [PATCH v3 0/2] qemu: support shmem device migration

Ping. > > Shmem device support property role with 'master'(master=on) or > 'peer'(master=off, default mode), which controls to copy the > shared memory on migration to the destination host or not. see > https://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/system/ivshmem.rst;hb=HEAD > > > The

RE: [PATCH 0/2] qemu: support shmem device migration

Please forget it and review the V3. Sorry :-( > > Shmem device support property role with 'master'(master=on) or > 'peer'(master=off, default mode), which controls to copy the > shared memory on migration to the destination host or not. see >

RE: [PATCH v2 2/2] qemu: allow configuring mem-path for ivshmem-plain device

> On Fri, Jul 17, 2020 at 09:04:51PM +0800, Wang Xin wrote: > >The shared memory path is generated by shmem name as default, > >however, we may need to change it to avoid filename conflict > >when VM migrate to other host. > > > > At which point there is no need for the name at all. I agree that

RE: [PATCH v2 1/2] qemu: add support for shmem-{plain, doorbell} role

> On Fri, Jul 17, 2020 at 09:04:50PM +0800, Wang Xin wrote: > >Role(master or peer) controls how the domain behaves on migration. > >For more details about migration with ivshmem, see > >https://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/system/ivshmem.rst;hb=HEAD > > > >It's a optional

RE: [question]qemu: any plan to support ivshmem-plain migration?

> -Original Message- > From: Daniel P. Berrangé [mailto:berra...@redhat.com] > Sent: Monday, July 6, 2020 9:48 PM > To: Wangxin (Alexander, Cloud Infrastructure Service Product Dept.) > > Cc: libvir-list@redhat.com; mklet...@redhat.com; Huangweidong (C) > > Sub

[question]qemu: any plan to support ivshmem-plain migration?

Hi, Martin Ivshmem-plain device support property role with 'master'(master=on) or 'peer'(master=off, default mode), which controls to copy the shared memory on migration to the destination host or not.