On Thu, Jun 9, 2022 at 3:01 AM Bertrand Marquis <Bertrand.Marquis@...> wrote:
On 9 Jun 2022, at 10:57, Michal Orzel via lists.yoctoproject.org <michal.orzel=arm.com@...> wrote:
By default, highmem option is enabled for machine types later than virt-2.12. This allows qemu to place devices and RAM in physical address space above 32-bits. This can cause issues as according to the documentation Xen supports up to 12GiB of physical address space. Recently the issue was observed using runqemu, that was causing Linux running on top of Xen to stall when trying to access ECAM space placed by qemu at 256GiB mark. Even though this issue is most probably related to QEMU and not Xen (the investigation showed that it can map ECAM space correctly), it is best to avoid such issues by disabling highmem on qemuarm.
# 64-bit Arm: gic version 3 QB_MACHINE:qemuarm64 = "-machine virt,gic-version=3 -machine virtualization=true" -# 32-bit Arm -QB_MACHINE:qemuarm = "-machine virt -machine virtualization=true" +# 32-bit Arm: highmem=off +# Disable highmem so that qemu does not use highmem IO regions that end up +# being placed at the 256GiB mark (e.g. ECAM space) and can cause issues in Xen. +QB_MACHINE:qemuarm = "-machine virt,highmem=off -machine virtualization=true"
# Increase the default qemu memory allocation to allow for the hypervisor. # Use a weak assignment to allow for change of default and override elsewhere. -- 2.25.1