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

[Alexandre Kouznetsov <alk@xxxxxxxxxx>]

Hello.

El 22/07/13 18:41, Brian Menges escribió:
> This isn't an 'xm' compatible system, xe is the toolstack in use here.
Sorry, my fault.
Maybe xl command is present then?
"xl dmesg | less" should do.

> 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?
Not sure if it have to be modified in two places.

An earlier article http://support.citrix.com/article/CTX126531 instructs 
to alter the booting parameter and the XAPI database, while a later one 
http://support.citrix.com/article/CTX134951 seems to take into account 
only the boot parameter. They introduced a specialized script 
(http://support.citrix.com/article/CTX134951), which, apparently, does 
the same as editing the bootloadre configuration by hand.
If you ask me, do the less alterations possible. I would expect dom0_mem 
on the boot command line to be enough.
Actually, dom0_mem goes on the hypervisor's itself command line, 
regardless the bootloader used (grub or syslinux or whatever). So a 
reference that talks about another bootloader should work for your case.
Make sure Grub does takes into account the changes you have made.

Can't tell much about the priority.

Greetings

> -----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
>
> Hello.
>
> 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
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api