> On Wed, Jan 28, 2009 at 3:33 PM, Fajar A. Nugraha <fajar@xxxxxxxxx> wrote:
>> On Wed, Jan 28, 2009 at 7:20 PM, Heiko <rupertt@xxxxxxxxx> wrote:
>>> Hello again.
>>>
>>> it seems xen is ignoring this parameter.
>>> I did set it but, the domU still take CPU 0.
>>>
>>> i did:
>>>
>>> #xm vcpu-set 0 1
>>> #xm vcpu-pin 0 0 0
>>
>> This one only affects dom0, it doesn't affect any domU.
>>
>>>
>>> and put cpus="^0" into my domU configs
>>>
>>
>> Did you start/restart the domU after changing those config? If not,
>> and you don't want to restart domU, then you need to manually pin each
>> domU that's using CPU0 to other CPUs. See "xm vcpu-pin" for command
>> line help.
>>
>> If yes, what OS/xen version are you using?
>> What does "xm create --help_config | grep cpu" say?
>> What does "man xmdomain.cfg" says about cpus?
>>
>
> Hello,
> i did stop the domU and started it manually, they till used CPU0
> when i put cpus="1,2,3" there it works.
I've seen the problem before. What I needed to do was"
cpus="0-n,^0"
where n=(number of cores in the system - 1).
Ex. 4 core system
cpus="0-3,^0"
will allow the domU's to share CPU's 1,2,3 and not use CPU0 (reserved for
Dom0)
> The manpage says I can use the negation,
> the grep give me this:
> cpus=CPUS CPUS to run the domain on.
>
> manually pinning the cores work also fine:
>
> prod_rd_vpn 2 0 2 -b- 155.4 1-3
> prod_rd_vpn 2 1 1 -b- 123.4 1-3
>
> I am using CentOS 5.2
>
> greetings
>
> .r
>
>> Regards,
>>
>> Fajar
>>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|