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: [Xen-devel] Re: [Xen-changelog] [xen-3.1-testing] xend: fix server/n

To: David Edmondson <dme@xxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-changelog] [xen-3.1-testing] xend: fix server/netif.py so that it respects type=None.
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Fri, 5 Oct 2007 18:57:21 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, John Levon <levon@xxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 05 Oct 2007 10:58:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071005173622.GN1326@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20071005143301.GC1326@xxxxxxxxxxxxxxxxxx> <C32C1D3C.167B6%Keir.Fraser@xxxxxxxxxxxx> <20071005160656.GC8249@xxxxxxxxxx> <20071005161635.GG1326@xxxxxxxxxxxxxxxxxx> <20071005173048.GA30405@xxxxxxxxxx> <20071005173622.GN1326@xxxxxxxxxxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Fri, Oct 05, 2007 at 06:36:22PM +0100, David Edmondson wrote:
> On Fri, Oct 05, 2007 at 06:30:48PM +0100, Daniel P. Berrange wrote:
> > > The whole "PV and IOEMU" at the same time makes me uncomfortable,
> > > though it looks to be more problematic with disks than network
> > > devices.
> > 
> > The key is that the Dom0 configuration of the guest should allow the
> > guest kernel to choose the drivers.
> 
> Understood.
> 
> > Obviously you don't want both drivers active at once, so one idea is
> > for the PV drivers to 'grab' the PCI resources associated with the
> > emulated NIC.
> 
> That seems so wrong.
> 
> In Solaris drivers are loaded as a result of a mapping from the PCI ID
> of the device to a driver name (I've no idea if it's the same in
> Linux). What happens if the RTL8139 driver gets in first?

If the PV driver is unable to grab the PCI resources of the RTL NIC
because RTL8139 is already loaded, then it wouldn't try to initialize 
the PV nic. So this basically provides the safety net against both
being active (accidentally or by delibrate admuin actions). Then you 
need to figure out a way to prioritization the driver you really want.

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  -=| 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>