Re: [PATCH 2/2] qmp: Expose MachineClass::default_ram_id

2020-05-26 Thread Michal Privoznik
On 5/25/20 8:06 PM, Eduardo Habkost wrote: On Mon, May 25, 2020 at 07:03:28PM +0200, Michal Privoznik wrote: If a management application (like Libvirt) want's to preserve migration ability and switch to '-machine memory-backend' it needs to set exactly the same RAM id as QEMU would. Since the id

Re: [PATCH 2/2] qmp: Expose MachineClass::default_ram_id

2020-05-25 Thread Eduardo Habkost
On Mon, May 25, 2020 at 07:03:28PM +0200, Michal Privoznik wrote: > If a management application (like Libvirt) want's to preserve > migration ability and switch to '-machine memory-backend' it > needs to set exactly the same RAM id as QEMU would. Since the id > is machine type dependant, expose it

[PATCH 2/2] qmp: Expose MachineClass::default_ram_id

2020-05-25 Thread Michal Privoznik
If a management application (like Libvirt) want's to preserve migration ability and switch to '-machine memory-backend' it needs to set exactly the same RAM id as QEMU would. Since the id is machine type dependant, expose it under 'query-machines' result. Signed-off-by: Michal Privoznik --- hw/c