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

To:	"Ryan Harper" <ryanh@xxxxxxxxxx>, "aq" <aquynh@xxxxxxxxx>
Subject:	RE: [Xen-devel] [PATCH] enforce dom0 cpus and balloon out memory
From:	"Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date:	Fri, 29 Jul 2005 18:26:04 +0100
Cc:	xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Fri, 29 Jul 2005 17:24:32 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcWUUKasUmIiu4foToKrmG7o3Tf/jAAEKe8A
Thread-topic:	[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.
> 
> 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?

Ian

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