This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] enforce dom0 cpus and balloon out memory
From: Ryan Harper <ryanh@xxxxxxxxxx>
Date: Fri, 29 Jul 2005 13:26:13 -0500
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ryan Harper <ryanh@xxxxxxxxxx>
Delivery-date: Fri, 29 Jul 2005 18:25:04 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5b7eb71db65359027378e41e0c19f877@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D282851@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <5b7eb71db65359027378e41e0c19f877@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6+20040907i
* Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> [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:


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


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

Xen-devel mailing list