From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kip Macy Subject: Re: "virtual cluster" debug support Date: Sat, 19 Mar 2005 14:41:12 -0800 Message-ID: References: Reply-To: Kip Macy Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit In-Reply-To: Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Ian Pratt Cc: Xen Developers , ian.pratt@cl.cam.ac.uk List-Id: xen-devel@lists.xenproject.org > (though create will fill in a default of groupid = domid). That restriction is only a current limitation of the tools. I simply haven't taken the time to set the option at runtime. > I'm not keen on the proliferation of dom0 ops, and I expect we'll merge > a number of them into a 'get/set domain parameter' operation at some What is wrong with {GET/SET}DOMAININFO? These can be done at run-time. If you look, you'll see that I explicitly handle the case of removing a domain from an existing group before adding it to another. > point, but for the moment, I think the best soloution is adding a > DOM0_SETDOMAINGROUP. I'm perfectly happy to do that, but I'd like to know why SETDOMAININFO doesn't fit the bill. I would also appreciate feedback on the correctness of the locking. Thanks. -Kip ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click