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] Xen 3.0 Status update

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 3.0 Status update
From: aq <aquynh@xxxxxxxxx>
Date: Fri, 29 Jul 2005 11:30:30 +0900
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 29 Jul 2005 02:28:59 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SlxRDgjw3YcgzVA+MdYeJLPYHpzI8OqN6DibGgloAXgifEJb7IMRiyn3HpgjF5cU7a4e/rPkNqk0c1xPeWY3+DplYoC5hFyVU+Qo4/5fBlJNqK7EqR6T7Szd1to3ipzooGpoFQGNEjbFuxbkgTxJRhtJB7jipD0Y4ZXYfn9F/iY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D282807@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <A95E2296287EAD4EB592B5DEEFCE0E9D282807@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: aq <aquynh@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 7/28/05, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> wrote:
> > > We need to complete the XenBus/XenStore switchover. Block
> > devices are
> > > basically done
> >
> > Have it checked in yet?
> 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.

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?
> 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.

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.



Xen-devel mailing list