From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ben Thomas <bthomas@virtualiron.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: GPL release of Virtual Iron sources
Date: Tue, 3 Oct 2006 21:37:18 +0100 [thread overview]
Message-ID: <20061003203718.GD29356@redhat.com> (raw)
In-Reply-To: <4522A716.9070903@virtualiron.com>
On Tue, Oct 03, 2006 at 02:08:22PM -0400, Ben Thomas wrote:
> Some of the more interesting features are:
>
> - a different control plane model in domain-0 (no user accessible
> environment, no Python, no xen* daemons, etc)
This is intriguing - do you have any docs about this alternate control
plane which elaborate on its architecture & API, and the benefits it
brings over the current control plane ? When 3.0.4 development starts,
the new control API will be one of the core bits of work so understanding
this work you've done is very topical. Even if there's no desire to do
wholesale replacement of the Python daemons, ideas/lessons learnt from
the API / network protocols may well be valuable.
> - source code for domain-0 and hypervisor
> See http://www.virtualiron.com/products/open_source.cfm
Is the alternate Dom0 control plane agent code here compatible with the
current Xen unstable/3.0.3 HV & Dom0 kernel, or does it have dependancies
on changes you made to HV / dom0 too ?
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
prev parent reply other threads:[~2006-10-03 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 18:08 GPL release of Virtual Iron sources Ben Thomas
2006-10-03 18:43 ` Anthony Liguori
2006-10-09 20:56 ` Ben Thomas
2006-10-09 21:08 ` Anthony Liguori
2006-10-03 20:37 ` Daniel P. Berrange [this message]
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=20061003203718.GD29356@redhat.com \
--to=berrange@redhat.com \
--cc=bthomas@virtualiron.com \
--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.