On Fri, Apr 23, 2021 at 15:24:28 +0200, Michal Privoznik wrote: > Nothing special is happening here. All important changes were > done when for 'virtio-pmem' (adjusting the code to put virtio > memory on PCI bus, generating alias using > qemuDomainDeviceAliasIndex(). The only bit that might look > suspicious is no prealloc for virtio-mem. But if you think about > it, the whole purpose of this device is to change amount of > memory exposed to guest on the fly. There is no point in locking > the whole backend in memory. > > Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx> > --- > src/qemu/qemu_alias.c | 9 +++- > src/qemu/qemu_command.c | 12 +++++- > ...mory-hotplug-virtio-mem.x86_64-latest.args | 41 +++++++++++++++++++ > tests/qemuxml2argvtest.c | 1 + > 4 files changed, 60 insertions(+), 3 deletions(-) > create mode 100644 tests/qemuxml2argvdata/memory-hotplug-virtio-mem.x86_64-latest.args Reviewed-by: Peter Krempa <pkrempa@xxxxxxxxxx>
