mirror of
git://git.yoctoproject.org/meta-virtualization.git
synced 2025-07-19 20:59:41 +02:00
b9a94a5fb6
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. Signed-off-by: Michal Orzel <michal.orzel@arm.com> Reviewed-by: Bertrand Marquis <bertrand.marquis@arm.com> Reviewed-by: Christopher Clark <christopher.w.clark@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> |
||
|---|---|---|
| .. | ||
| cni_networking.bbclass | ||
| image-oci-sloci-image.inc | ||
| image-oci-umoci.inc | ||
| image-oci.bbclass | ||
| meta-virt-cfg.bbclass | ||
| meta-virt-hosts.bbclass | ||
| meta-virt-k8s-cfg.bbclass | ||
| meta-virt-xen-cfg.bbclass | ||
| qemuboot-testimage-network.bbclass | ||
| qemuboot-xen-defaults.bbclass | ||
| qemuboot-xen-dtb.bbclass | ||
| sanity-meta-virt.bbclass | ||