From: Andrew Warfield <andrew.warfield@gmail.com>
To: Jacob Gorm Hansen <jacobg@diku.dk>
Cc: Anthony Liguori <anthony@codemonkey.ws>, Xen-devel@lists.sourceforge.net
Subject: Re: x2d2
Date: Wed, 19 Jan 2005 10:12:28 +0000 [thread overview]
Message-ID: <eacc82a405011902127510dbc3@mail.gmail.com> (raw)
In-Reply-To: <41EE2F56.6090304@diku.dk>
We are in the process of some fairly major revisions to the control
tools. I think that the general expectation is that 3.0 will show
some pretty big changes to the control interfaces and tools. The
unstable tree now has a control switch (xcs) which sits under xend and
allows other applications to be written to use the control channels
without needing to modify xend. We are hoping to move towards small,
single-purpose management tools in dom0.
This should all start to appear in the unstable tree over the next
couple of months.
a.
On Wed, 19 Jan 2005 01:58:46 -0800, Jacob Gorm Hansen <jacobg@diku.dk> wrote:
> Anthony Liguori wrote:
> > Jacob Gorm Hansen wrote:
> >
> >> hi,
> >>
> >> is x2d2 (the minimal xend replacement in C if I understand correctly)
> >> still alive? I do not have bk at the moment, but grepping on x2d2 in
> >> the Changelog file only has a comment back from November. I can make
> >> it compile by removing -Werror from the Makefile, but is anyone using
> >> it and working on it, or is it a dead end?
> >
> >
> > I don't think so. It shouldn't actually work anymore. It doesn't do
> > proper notifications on event channels. There's also a bug in the way
> > ports are allocated.
> >
> > Is there still interest in x2d2 (or any C-based minimal xend)? I think
> > I could fix x2d2 pretty easily.
> >
>
> Yes, lots of interest from me, the python xend effectively keeps me from
> running Xen 2.0, so I am still stuck with 1.3. The stock xend uses too
> much memory, provides too much functionality, and depends on too many
> third-party packages -- not the ideal specs for the minimal trusted
> computing base I am trying to develop :-(
>
> Jacob
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next prev parent reply other threads:[~2005-01-19 10:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 2:19 x2d2 Jacob Gorm Hansen
2005-01-19 4:20 ` x2d2 Ronald G. Minnich
2005-01-19 6:32 ` x2d2 Anthony Liguori
2005-01-19 9:58 ` x2d2 Jacob Gorm Hansen
2005-01-19 10:12 ` Andrew Warfield [this message]
2005-01-19 14:11 ` x2d2 Anthony Liguori
2005-01-19 16:36 ` x2d2 Ian Pratt
2005-01-19 16:44 ` x2d2 Andrew Warfield
2005-01-19 20:12 ` x2d2 Ronald G. Minnich
2005-01-21 0:22 ` x2d2 Michael Hohnbaum
2005-01-21 0:35 ` x2d2 Andrew Warfield
2005-01-19 15:47 ` x2d2 Ronald G. Minnich
2005-01-19 19:01 ` x2d2 Anthony Liguori
2005-01-19 18:55 ` x2d2 Ronald G. Minnich
2005-01-20 14:08 ` x2d2 Rik van Riel
2005-01-20 18:36 ` x2d2 Rik van Riel
2005-01-20 22:45 ` x2d2 Felipe Alfaro Solana
2005-01-19 23:24 ` x2d2 Adam Sulmicki
2005-01-19 12:00 ` x2d2 Grzegorz Milos
-- strict thread matches above, loose matches on Subject: below --
2005-01-19 19:19 x2d2 Anthony Liguori
2005-01-19 20:37 x2d2 Ian Pratt
2005-01-19 20:38 ` x2d2 Ronald G. Minnich
2005-01-19 21:23 ` x2d2 Anthony Liguori
2005-01-19 20:43 x2d2 Ian Pratt
2005-01-19 21:03 ` x2d2 Derrik Pates
2005-01-19 21:17 ` x2d2 Ronald G. Minnich
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=eacc82a405011902127510dbc3@mail.gmail.com \
--to=andrew.warfield@gmail.com \
--cc=Xen-devel@lists.sourceforge.net \
--cc=andrew.warfield@cl.cam.ac.uk \
--cc=anthony@codemonkey.ws \
--cc=jacobg@diku.dk \
/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.