aboutsummaryrefslogtreecommitdiff
path: root/tests/avocado/mem-addr-space-check.py
diff options
context:
space:
mode:
Diffstat (limited to 'tests/avocado/mem-addr-space-check.py')
-rw-r--r--tests/avocado/mem-addr-space-check.py9
1 files changed, 4 insertions, 5 deletions
diff --git a/tests/avocado/mem-addr-space-check.py b/tests/avocado/mem-addr-space-check.py
index af019969c0..85541ea051 100644
--- a/tests/avocado/mem-addr-space-check.py
+++ b/tests/avocado/mem-addr-space-check.py
@@ -31,11 +31,10 @@ class MemAddrCheck(QemuSystemTest):
at 4 GiB boundary when "above_4g_mem_size" is 0 (this would be true when
we have 0.5 GiB of VM memory, see pc_q35_init()). This means total
hotpluggable memory size is 60 GiB. Per slot, we reserve 1 GiB of memory
- for dimm alignment for all newer machines (see enforce_aligned_dimm
- property for pc machines and pc_get_device_memory_range()). That leaves
- total hotpluggable actual memory size of 59 GiB. If the VM is started
- with 0.5 GiB of memory, maxmem should be set to a maximum value of
- 59.5 GiB to ensure that the processor can address all memory directly.
+ for dimm alignment for all machines. That leaves total hotpluggable
+ actual memory size of 59 GiB. If the VM is started with 0.5 GiB of
+ memory, maxmem should be set to a maximum value of 59.5 GiB to ensure
+ that the processor can address all memory directly.
Note that 64-bit pci hole size is 0 in this case. If maxmem is set to
59.6G, QEMU should fail to start with a message "phy-bits are too low".
If maxmem is set to 59.5G with all other QEMU parameters identical, QEMU