> You could use vcpu-hotplug to drop the extra cpus from dom0 instead of
> writing directly into sysfs. The only stopper to that approach is the
> fact that dom0's self.channel is not initialized when xend starts and
> subsequently doesn't send the control message. Channels are initialized
> when a domain is built, but since dom0 is built by xen, the routine
> which sets up channels isn't called for dom0. Haven't found a good place
> for xend to initialized the channel for dom0 yet either.
Hmmm. Is the channel never set up then? It'd certainly be nice if it were: 
then you can use "xm balloon" to set dom0's memory footprint, which is 
preferable to using the /proc interface directly.
Cheers,
Mark
>
> See vcpu_hotplug() in xen/xend/XendDomInfo.py
>
> 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 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel