qemu-server/PVE
Thomas Lamprecht 33b0d3b7be memory hotplug: rework max memory handling, make phys-bits dependent
QEMU 7.1 introduced some actual checks for the max memory value in
1caab5cf86bd ("i386/pc: bounds check phys-bits against max used GPA")
and while correct it breaks our by-luck working hard coded max mem of
4 TB for cases with smaller phys bit address sizes, like some older
CPUs or most CPU types have per default if not 'host' or 'max'.

QEMU uses 40 bits per default if the CPU isn't set to host or
phys-bits is not set explicitly.

For 40 bit it seems that depending on machine type one has a max
possible mem of: i440 -> 752, q35 -> 722 GiB, but instead of reducing
it to 704 GiB (512+1128+64) in a hard coded way we acutally check for
the bit size that will probably be used and use that to determine the
max memory size useable.

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2022-11-17 16:54:49 +01:00
..
API2 qm: add remote-migrate command 2022-11-17 15:21:39 +01:00
CLI qm: add remote-migrate command 2022-11-17 15:21:39 +01:00
QemuServer memory hotplug: rework max memory handling, make phys-bits dependent 2022-11-17 16:54:49 +01:00
VZDump vzdump : skip special:cloudinit section 2022-11-08 17:23:30 +01:00
Makefile buildsys: use $(MAKE) instead of make 2019-09-24 18:06:16 +02:00
QemuConfig.pm fix #4201: delete cloud-init disk on rollback 2022-11-11 19:26:16 +01:00
QemuMigrate.pm migrate: add remote migration handling 2022-11-17 15:21:39 +01:00
QemuServer.pm migrate: add remote migration handling 2022-11-17 15:21:39 +01:00
QMPClient.pm qmp client: increase default fallback timeout to 5s 2022-09-16 13:01:45 +02:00