Mailing List Archive: Xen: API

Ubuntu 12.04 LTS + XCP-XAPI dom0_mem not obeyed

Index | Next | Previous | View Threaded

bmenges at gogrid

Jul 22, 2013, 12:07 PM

Post #1 of 5 (86 views)
Permalink

Ubuntu 12.04 LTS + XCP-XAPI dom0_mem not obeyed

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_DEFAULT="Xen 4.1-amd64"
GRUB_HIDDEN_TIMEOUT=10
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX="apparmor=0"
GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=4096M,max:4096M dom0_max_vcpus=2 com1=115200,8n1 console=com1,vga"

Am I missing something here? I can never get the memory I want out of these settingsā€¦ itā€™s as if the kernel is completely ignoring them. Iā€™ve tried with/without the max segment, and all sorts of searches have turned up nothing. Are there XAPI settings too? I thought that /etc/xen/xend-config.sxp wasnā€™t in play with XAPI, but I could modify that!

Uhā€¦ sore forehead, anyone care to help me out here so I can issue the correct face palm to myselfā€¦ I have to be missing something.

- Brian Menges
Principal Engineer, DevOps
GoGrid | ServePath | ColoServe | UpStream Networks

________________________________

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.

alk at ondore

Jul 22, 2013, 3:59 PM

Post #2 of 5 (82 views)
Permalink

Re: Ubuntu 12.04 LTS + XCP-XAPI dom0_mem not obeyed [In reply to]

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 [at] lists
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

bmenges at gogrid

Jul 22, 2013, 4:41 PM

Post #3 of 5 (82 views)
Permalink

Re: Ubuntu 12.04 LTS + XCP-XAPI dom0_mem not obeyed [In reply to]

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 [at] lists [mailto:xen-api-bounces [at] lists] On Behalf Of Alexandre Kouznetsov
Sent: Monday, July 22, 2013 16:02
To: xen-api [at] lists
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 [at] lists
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

________________________________

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
Xen-api [at] lists
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

alk at ondore

Jul 22, 2013, 5:22 PM

Post #4 of 5 (83 views)
Permalink

Re: Ubuntu 12.04 LTS + XCP-XAPI dom0_mem not obeyed [In reply to]

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 [at] lists [mailto:xen-api-bounces [at] lists] On Behalf Of Alexandre Kouznetsov
> Sent: Monday, July 22, 2013 16:02
> To: xen-api [at] lists
> 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 [at] lists
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

bmenges at gogrid

Jul 22, 2013, 5:55 PM

Post #5 of 5 (82 views)
Permalink

Re: Ubuntu 12.04 LTS + XCP-XAPI dom0_mem not obeyed [In reply to]

My dom0 only took up the ~4g memory after I modified the control domain entry in xapi. The boot parameter at grub did nothing; and I verified several times that it was passed correctly. It does work for the vcpus, but not for memory.

- Brian Menges
Principal Engineer, DevOps
GoGrid | ServePath | ColoServe | UpStream Networks

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

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 [at] lists
> [mailto:xen-api-bounces [at] lists] On Behalf Of Alexandre
> Kouznetsov
> Sent: Monday, July 22, 2013 16:02
> To: xen-api [at] lists
> 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 [at] lists
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

________________________________

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
Xen-api [at] lists
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads