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

[Ryan Harper <ryanh@us.ibm.com>]

* Keir Fraser <Keir.Fraser@cl.cam.ac.uk> [2005-07-29 13:20]:
> 
> On 29 Jul 2005, at 18:26, Ian Pratt wrote:
> 
> >>
> >>See vcpu_hotplug() in xen/xend/XendDomInfo.py
> >
> >Yep, I'd much prefer this approach -- its annoying the tools don't work
> >on dom0. Volunteers?
> 
> They certainly *ought* to work. I can assure you that xend does connect 
> to domain0's control interface. Otherwise you could not set up virtual 
> blkif and netif connections to backend drivers running in domain0!
> 
> This should be a small bugfix: no major implementation effort required. 
> :-)

Agreed.  It is a simple matter of find the right place in the xend code
to initialize the self.channel (calling crate_channel()) for dom0.

I reported this a while ago.  _something_ is wrong with self.channel in
XendDomInfo object for dom0 as I noted in this message:

http://lists.xensource.com/archives/html/xen-devel/2005-07/msg00444.html

Also in bugzilla #101, I added a patch to show that the control message
wasn't sent because the channel is not valid.

http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=101


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