On 2 May 2018 at 11:41, Laszlo Ersek <ler...@redhat.com> wrote: > What about guest RAM size (more precisely, guest-phys address space)? > > The x86_64 target might want to use tens of GBs of guest-phys address > space, e.g. for cold-plugged RAM, for DIMM hotplug, for 64-bit PCI MMIO > aperture. To my understanding, all of those have to be expressed with > host virtual addresses in the QEMU process (regardless of TCG vs. KVM). > But on a 32-bit host, the QEMU process only has 4GB HVA space.
I think the situation there would be unchanged -- on a 32 bit host the ramaddr type is 32 bits (unless Xen is configured into the binary!) regardless of the guest architecture size, and the limit on RAM size is 2GB, and the hwaddr is 64 bits regardless of guest architecture size. That wouldn't change whether we had a single executable or split ones for 32 and 64 bit targets. You can have more than 4GB of guest physical address space (we don't map that into the host address space), but there's a 2GB RAM limit (because we do map all the RAM blocks); these limits currently apply equally to qemu-system-i386 and qemu-system_x86-64. thanks -- PMM
