From mboxrd@z Thu Jan 1 00:00:00 1970 From: aq Subject: Re: Xen 3.0 Status update Date: Fri, 29 Jul 2005 11:30:30 +0900 Message-ID: <9cde8bff0507281930db7a6ff@mail.gmail.com> References: Reply-To: aq Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On 7/28/05, Ian Pratt wrote: >=20 > > > We need to complete the XenBus/XenStore switchover. Block > > devices are > > > basically done > > > > Have it checked in yet? >=20 > The code to switch block devices over isn't checked in yet, the rest of > it is. It's not quite ready for checking in yet, but I think it got > posted to xen-tools. >=20 unfortunately i havent seen anything posted in that mailing list. the only message archived of that list so far is a "welcome" mail. > > > There are a bunch of small outstanding tools issues we need > > to address: > > > * sanitize all the xm commnds to give them consistent naming and > > > parameters > > > * test error paths > > > * split console from xend and replace control messages with XenBus > > > (1st part complete) > > > * fix output of 'xm info' > > > > oops, i will re-submit the patch to show xen version. but > > what is wrong with "xm info" at the moment? >=20 > Last time I looked, we weren't exporting all the information available > e.g. num logical cpus, num nodes, sockets per node. Also we should > export the Xen architecture as {x86_32, x86_32p, x86_64} rather than > reporting the dom0 architecture. >=20 ok, i will submit the patch for this problem > Also, please can you repost you dom0-mem-min and dom0-num-cpus patch to > the list for general review. >=20 ok. regards, aq