From: aq <aquynh@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Xen 3.0 Status update
Date: Fri, 29 Jul 2005 11:30:30 +0900 [thread overview]
Message-ID: <9cde8bff0507281930db7a6ff@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282807@liverpoolst.ad.cl.cam.ac.uk>
On 7/28/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> 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.
>
ok.
regards,
aq
next prev parent reply other threads:[~2005-07-29 2:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 11:52 Xen 3.0 Status update Ian Pratt
2005-07-29 2:30 ` aq [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-29 11:16 Ian Pratt
2005-07-29 12:58 ` Gerd Knorr
2005-07-28 23:31 Ian Pratt
2005-07-28 23:05 Ian Pratt
2005-07-28 21:59 ` Scott Parish
2005-07-29 9:06 ` Gerd Knorr
2005-07-29 10:17 ` Keir Fraser
2005-07-28 22:39 Ian Pratt
2005-07-28 21:43 ` Scott Parish
2005-07-28 22:57 ` Mark Williamson
2005-07-28 21:55 ` Scott Parish
2005-07-28 21:35 Ian Pratt
2005-07-28 20:30 ` Scott Parish
2005-07-28 21:15 Ian Pratt
2005-07-28 20:09 ` Scott Parish
2005-07-28 21:01 Walker, Bruce J (HP-Labs)
2005-07-27 23:34 Ian Pratt
2005-07-28 4:28 ` aq
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9cde8bff0507281930db7a6ff@mail.gmail.com \
--to=aquynh@gmail.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.