[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] dom0 dedicated memory Xen dom0 dedicated memory and preventing dom0 memory ballooning

  • To: Xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Barny Kadlecsik <xen@xxxxxxxxxxxx>
  • Date: Mon, 06 Jun 2011 18:20:08 +0200
  • Cc:
  • Delivery-date: Mon, 06 Jun 2011 09:21:09 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I'm trying to configure GRUB to allocate fixed amount of dedicated memory to dom0, according to this best practices thread (http://wiki.xensource.com/xenwiki/XenBestPractices | "Xen dom0 dedicated memory and preventing dom0 memory ballooning "). When I reboot, dom0 has the fixed amount of memory as it was configured, but neither xm info shows the rest of memory available for the Hypervisor, nor can start domUs (due to lack of memory). For me it seems that the memory over the configured dom0_mem parameter is somehow invisible to the Hypervisor and both dom0/dumUs are unable to use it.

Is the given best practices article broken, or am I missing something?

Debian Squeeze
ii linux-image-2.6.32-5-xen-amd64 2.6.32-34squeeze1 Linux 2.6.32 for 64-bit PCs, Xen dom0 support ii xen-hypervisor-4.0-amd64 4.0.1-2 The Xen Hypervisor on AMD64

Thank you in advance!

Barny Kadlecsik

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.