On Wed, Jan 28, 2009 at 10:14 PM, Ryan Burke <burke@xxxxxxxxxxxxxxxxx> wrote:
>> 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)
>
That's weird. I've been using both RHEL 5.2 and 5.3, with RH's stock
Xen, both behaved properly (e.g. cpus="^0") works fine. Good hint on
the workaround though, I'll keep that in mind if I see similar
problem.
On a side note, my Xen version (RH's xen-3.0.3-80.el5) seems to be
capable of doing automatic vcpu rebalancing. i.e. starting a new
domain can cause other domain's CPU allocation to change
automatically. I've tried shutting and starting a domU several times,
resulting the other domUs to have their CPU allocation change, but
none of them uses CPU0. So all I can say is that perhaps this Xen
version properly recognize "cpus=^0" while Heiko's don't. Updating
might help.
Regards,
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home