DescriptionMichal Privoznik
2020-10-12 09:17:04 UTC
+++ This bug was initially created as a clone of Bug #1839034 +++
Description of problem:
When libvirt wants to use memory-backend-* even for regular guest memory it needs to know the default RAM ID which was exposed by the following commit:
commit c556600598afc6e90ae52a2e9ce910b8842244c5
Author: Michal Privoznik <mprivozn>
AuthorDate: Tue May 26 10:25:35 2020 +0200
Commit: Eduardo Habkost <ehabkost>
CommitDate: Wed Aug 19 10:45:21 2020 -0400
qmp: Expose MachineClass::default_ram_id
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. Some machine types don't have the attribute set (riscv
family for example), therefore the QMP attribute must be
optional.
Signed-off-by: Michal Privoznik <mprivozn>
Message-Id: <9384422f63fe594a54d801f9cb4539b1d2ce9b67.1590481402.git.mprivozn>
Reviewed-by: Igor Mammedov <imammedo>
[ehabkost: updated doc to "since 5.2"]
Signed-off-by: Eduardo Habkost <ehabkost>
https://git.qemu.org/?p=qemu.git;a=commit;h=c556600598afc6e90ae52a2e9ce910b8842244c5
If the default RAM ID is not exposed then libvirt falls back to the old (deprecated?) -mem-path.