d/[..]/grub.d/xen.cfg: dom0_mem max IS needed

I misread the upstream documentation. Adding max: for x86 is actually
necessary to not have it "attempt to allocate enough page tables to
cover all of *host* RAM which can exhaust its actual memory allocation".

Signed-off-by: Hans van Kranenburg <hans@knorrie.org>

diff --git a/debian/tree/xen-hypervisor-common/etc/default/grub.d/xen.cfg b/debian/tree/xen-hypervisor-common/etc/default/grub.d/xen.cfg
index a5559e10354cbac09c4e57a39c3d83ba06a1984a..e3853c33caa0904ed1713d76f0452b28beae659d 100644 (file)
--- a/debian/tree/xen-hypervisor-common/etc/default/grub.d/xen.cfg
+++ b/debian/tree/xen-hypervisor-common/etc/default/grub.d/xen.cfg
@@ -13,11 +13,12 @@ echo "Including Xen overrides from /etc/default/grub.d/xen.cfg"
 # The first two options are used to generate arguments for the hypervisor.
 # Commonly used options are:
 #
-# dom0_mem=<size>
+# dom0_mem=<size> (for arm)
+# dom0_mem=<size>,max:<size> (for x86)
 #   Sets the amount of memory dom0 uses to a fixed size. All other memory
 #   will be usable for domUs. For x86, this prevents ballooning actions
 #   from happening to take away memory from the dom0 or return it back. For
-#   arm, setting this option is required. E.g. dom0_mem=4G
+#   arm, setting this option is required. E.g. (for x86) dom0_mem=4G,max:4G
 #
 # dom0_max_vcpus=<min>-<max>
 #   Limits the amount of physical cpus that dom0 is using, so it will not