diff options
| author | Michal Orzel <michal.orzel@arm.com> | 2022-06-09 11:57:48 +0200 |
|---|---|---|
| committer | Bruce Ashfield <bruce.ashfield@gmail.com> | 2022-06-20 12:08:37 -0400 |
| commit | b9a94a5fb6f608d53ddbfe2a60cbc8a670922550 (patch) | |
| tree | 0fad48003cd7ec5ed2e8b94635c662b37989ff3a /recipes-containers/docker-distribution | |
| parent | 17f3d28228341b5fc80ffcfa8847f4cfb74991bf (diff) | |
| download | meta-virtualization-b9a94a5fb6f608d53ddbfe2a60cbc8a670922550.tar.gz | |
xen: Disable highmem on qemuarm
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>
Diffstat (limited to 'recipes-containers/docker-distribution')
0 files changed, 0 insertions, 0 deletions
