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

Re: [Xen-API] Ubuntu 12.04 LTS + XCP-XAPI dom0_mem not obeyed

  • To: "xen-api@xxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxx>
  • From: Brian Menges <bmenges@xxxxxxxxxx>
  • Date: Mon, 22 Jul 2013 23:41:44 +0000
  • Accept-language: en-US
  • Delivery-date: Mon, 22 Jul 2013 23:41:58 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=january; d=gogrid.com; h=Received:Received:From:To:Subject:Thread-Topic:Thread-Index:Date:Message-ID:References:In-Reply-To:Accept-Language:Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator:x-originating-ip:Content-Type:Content-Transfer-Encoding:MIME-Version; b=SAZnFqTJMVQy8HazceEjocKelzUlkvFM2KwFw0sjCGSHY3iN1SSj4L3dOh14/px9SyqKWI2DMW1JlK/qWK5dO6gH+YwFGPYbGkrRQ8aAtFABkpsjUqwHaxJtC0V0HOWD;
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
  • Thread-index: AQHOhw7BoYGb66NDKEmaWn4IJv/bsplxxXwA//+RWmA=
  • Thread-topic: [Xen-API] Ubuntu 12.04 LTS + XCP-XAPI dom0_mem not obeyed

This isn't an 'xm' compatible system, xe is the toolstack in use here.

Inspecting the /var/log/xen/xend.log I find the following:

[2013-07-19 17:54:56 1808] DEBUG (XendDomainInfo:1794) Storing domain details: 
{'description': '', 'console/limit': '1048576', 'vm': 
'/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 
'online', 'memory/target': '2096768', 
'control/platform-feature-multiprocessor-suspend': '1', 'console/type': 
'xenconsoled', 'name': 'Domain-0'}

Does this mean that the dom0 memory footprint is controlled in the api 
configuration and not the grub command line?

On a hunch; I issued:

HOST=$(hostname) && xe vm-param-set uuid=<UUID> memory-dynamic-max=4294967296 
memory-dynamic-min=4294967296 memory-target=4294967296

That seems to have buffed my memory up. I also took the opportunity to bump 
priority up. Does anyone know if 1) that this was the correct way to do this, 
and 2) what the default scheduling priority is (is it 256?)
- Brian Menges
Principal Engineer, DevOps
GoGrid | ServePath | ColoServe | UpStream Networks

-----Original Message-----
From: xen-api-bounces@xxxxxxxxxxxxx [mailto:xen-api-bounces@xxxxxxxxxxxxx] On 
Behalf Of Alexandre Kouznetsov
Sent: Monday, July 22, 2013 16:02
To: xen-api@xxxxxxxxxxxxx
Subject: Re: [Xen-API] Ubuntu 12.04 LTS + XCP-XAPI dom0_mem not obeyed


El 22/07/13 14:07, Brian Menges escribió:
> I've been fighting this for some time now, trying to get xen up and
> running so I can virtualize an old windows box and stuff it in my
> high-memory Linux system, but for the life of me I cannot get this
> thing to obey dom0_mem.
> I've edited /etc/default/grub and ran sudo update-grub several times
> with differing settings, but it refuses to pick up the settings it
> appears. Here's my default grub file:
> [...]
> GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=4096M,max:4096M dom0_max_vcpus=2
> com1=115200,8n1 console=com1,vga"
Check if there is no other GRUB_CMDLINE_XEN_DEFAULT in the same file, later 
after the definition.

Make sure to run grub-update after you have altered /etc/default/grub, in order 
to force the actual grub.conf to be regenerated.

While booting, confirm interactively ('e' key over the Xen menu option) that 
the desired options are really present in the command line.

Inspect tho output of "xm dmesg", it mentions the command line that was used to 
load Xen at the very beginning.

Alexandre Kouznetsov

Xen-api mailing list


The information contained in this message, and any attachments, may contain 
confidential and legally privileged material. It is solely for the use of the 
person or entity to which it is addressed. Any review, retransmission, 
dissemination, or action taken in reliance upon this information by persons or 
entities other than the intended recipient is prohibited. If you receive this 
in error, please contact the sender and delete the material from any computer.

Xen-api mailing list



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