From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nuno Silva 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 Sender: xen-devel-admin@lists.sourceforge.net Message-ID: <4036F265.4040300@vgertech.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Ian Pratt Cc: Jeff Marshall , xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org 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