External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-10-24 23:13:10 +00:00
Code Issues Packages Projects Releases Wiki Activity
001fa58ad8
libvirt/tests/qemuxmlconfdata/memory-hotplug-virtio-mem-overlap-address.x86_64-latest.err

2 lines
123 B
Plaintext
Raw Normal View History

virDomainMemoryDefValidate: Check for overlapping memory devices As of v9.4.0-rc2~5 it is possible to specify guest address where a virtio-mem/virtio-pmem memory device is mapped to. What that commit forgot to introduce was a check for overlaps. And yes, this is technically an O(n^2) algorithm, as virDomainMemoryDefValidate() is called over each memory device and after this, virDomainMemoryDefValidate() also iterates over each memory device. But given there's usually only a handful of such devices, and this runs only when parsing domain XML I guess code readability wins over some less obvious solution. Resolves: https://issues.redhat.com/browse/RHEL-4452 Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2023-09-22 09:01:40 +00:00
unsupported configuration: memory device address [0x140000000:0x180000000] overlaps with other memory device (0x170000000)
Reference in New Issue Copy Permalink