mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-10-21 13:39:15 +00:00
f309db1f4d
Libvirt BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1175397 QEMU BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1170093 In qemu there are two interesting arguments: 1) -numa to create a guest NUMA node 2) -object memory-backend-{ram,file} to tell qemu which memory region on which host's NUMA node it should allocate the guest memory from. Combining these two together we can instruct qemu to create a guest NUMA node that is tied to a host NUMA node. And it works just fine. However, depending on machine type used, there might be some issued during migration when OVMF is enabled (see QEMU BZ). While this truly is a QEMU bug, we can help avoiding it. The problem lies within the memory backend objects somewhere. Having said that, fix on our side consists on putting those objects on the command line if and only if needed. For instance, while previously we would construct this (in all ways correct) command line: -object memory-backend-ram,size=256M,id=ram-node0 \ -numa node,nodeid=0,cpus=0,memdev=ram-node0 now we create just: -numa node,nodeid=0,cpus=0,mem=256 because the backend object is obviously not tied to any specific host NUMA node. Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
9 lines
457 B
Plaintext
9 lines
457 B
Plaintext
LC_ALL=C PATH=/bin HOME=/home/test USER=test LOGNAME=test QEMU_AUDIO_DRV=none \
|
|
/usr/bin/qemu -S -M pc -m 1024 -smp 2 \
|
|
-numa node,nodeid=0,cpus=0,mem=256 \
|
|
-object memory-backend-file,prealloc=yes,\
|
|
mem-path=/dev/hugepages1G/libvirt/qemu,size=768M,id=ram-node1 \
|
|
-numa node,nodeid=1,cpus=1,memdev=ram-node1 \
|
|
-nographic -monitor unix:/tmp/test-monitor,server,nowait -no-acpi -boot c -usb \
|
|
-hda /dev/HostVG/QEMUGuest1 -net none -serial none -parallel none
|