Re: [Xen-devel] [PATCH] enforce dom0 cpus and balloon out memory

> 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

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

Re: [Xen-devel] [PATCH] enforce dom0 cpus and balloon out memory, Ryan Harper

Next by Date:

Re: [Xen-devel] Re: [Xen-tools] [RFC] xm interface proposed changes, harry

Previous by Thread:

Re: [Xen-devel] [PATCH] enforce dom0 cpus and balloon out memory, Ryan Harper

Next by Thread:

Re: [Xen-devel] [PATCH] enforce dom0 cpus and balloon out memory, Ryan Harper

Indexes:

[Date] [Thread] [Top] [All Lists]