WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] dom0 got load of 80

On Wed, Jan 28, 2009 at 9:05 PM, Ryan Burke <burke@xxxxxxxxxxxxxxxxx> wrote:
>> Here's what I use on xend-config.sxp
>>
>> (dom0-cpus 1)
>> (dom0-min-mem 256)
>>
>> and on grub's menu.lst
>>
>>         kernel /xen.gz-2.6.18-128.el5 dom0_mem=512M dom0_vcpus_pin
>>
>
> Sorry for the thread jack, this will be short...
>
> This is the first I've heard of the "dom0_vcpus_pin" option. So that is
> the same as
>  xm vcpu-set 0 1
>  xm vcpu-pin 0 0 0
> where Dom0 will be pinned to CPU0 at boot?

It's the same as the vcpu-pin command line if you only assign one CPU to dom0.
The vcpu-set line is the equivalent of  (dom0-cpus 1) on xend-config.sxp

> What version of Xen did that
> option make its appearance?
>

Not sure. According to http://wiki.xensource.com/xenwiki/XenBooting ,
it's available since 3.0. I've been using it on RHEL 5's stock xen
(which is based on xen 3.1.2), and it works.

> If so, that would be nice since I've been pinning Dom0 to CPU0 in rc.local
> and that always seemed weird to pin after it had booted.

Yeah, that's what I did as well before I read the documentation :D

Regards,

Fajar

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users