From: Nuno Silva <nuno.silva@vgertech.com>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: Jeff Marshall <mars9050@uidaho.edu>, xen-devel@lists.sourceforge.net
Subject: Re: Subject: Re: Creating a local network within the GuestOS and r outing to an ext ernal network
Date: Sat, 21 Feb 2004 05:53:41 +0000 [thread overview]
Message-ID: <4036F265.4040300@vgertech.com> (raw)
In-Reply-To: <E1Aty5g-00033m-00@wisbech.cl.cam.ac.uk>
Hi!
Ian Pratt wrote:
>>While I agree that network-level filtering is an important part
>>of a complete system, I'm not so sure that it belongs in the
>>core, priveleged portion of xen.
>
>
> Then you'll be happy to here that this functionality is moving
> outside Xen and into a 'driver domain' in the new IO model.
>
Do you mean that (in a very simple view) Xen will take care of memory
and domain management and another domain (domain 0?) will take care of
every other piece of hardware like IDE, SCSI and NICs?
This would be very cool but, as I understand. Xen requires "hardware"
drivers to be event based, so the guest OS in domain 0 would need a
giant patch... Right?
And Xen will end up with a) the Xen core, b) "hardware domain" guest OS
patch and c) general guest patches. Now we have a) and c), only... :-)
Making the core small is very good, but enlarging the rest - the "guest"
universe - is not so good...
Maybe I didn't understand your sentence :-) Can you explain a bit more,
please? :-)
Thanks,
Nuno Silva
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next prev parent reply other threads:[~2004-02-21 5:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 19:58 Subject: Re: Creating a local network within the GuestOS and r outing to an ext ernal network Jeff Marshall
2004-02-20 0:00 ` Ian Pratt
2004-02-21 5:53 ` Nuno Silva [this message]
2004-02-21 8:12 ` Ian Pratt
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=4036F265.4040300@vgertech.com \
--to=nuno.silva@vgertech.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=mars9050@uidaho.edu \
--cc=xen-devel@lists.sourceforge.net \
/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.