Re: [Xen-devel] Setting dom0-cpus to 0 doesn't use all cpus asdocumented

[Ryan Harper <ryanh@xxxxxxxxxx>]

* Carb, Brian A <Brian.Carb@xxxxxxxxxx> [2006-05-09 10:58]:
> We discovered this when running the xm-test suite. One of the tests
> (01_enforce_dom0_cpus) changes the number of cpus by editing the
> xend-config.sxp file and restarting xend. Should this test be updated to
> use the method Ian suggested, to vary the number of cpus, rather than
> restarting xend?

As Ian said, it is for setting the value when xend starts which is what
the test is about.  However, the test should bring dom0 vcpus to the
max and then test enforcement down to 1 rather than assuming that dom0's
current value can be reduced.  Or, bail on the test if the current value
of dom0's online vcpus isn't > 2.

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@xxxxxxxxxx

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