WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: Subject: Re: [Xen-devel] Creating a local network within the GuestOS

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: Subject: Re: [Xen-devel] Creating a local network within the GuestOS and r outing to an ext ernal network
From: Nuno Silva <nuno.silva@xxxxxxxxxxxx>
Date: Sat, 21 Feb 2004 05:53:41 +0000
Cc: Jeff Marshall <mars9050@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 21 Feb 2004 05:56:11 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <E1Aty5g-00033m-00@xxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Organization: VGER, LDA
References: <E1Aty5g-00033m-00@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040122 Debian/1.6-1
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel