[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Which kernel CONFIG_XXX options correspond to which vif drivers?


  • To: Xen users mailing list <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Bruce Edge <bruce.edge@xxxxxxxxx>
  • Date: Fri, 25 Jun 2010 11:22:31 -0700
  • Delivery-date: Fri, 25 Jun 2010 11:23:49 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Lyv1jy4XI59vTNOvartPkOjm7pRckdV4N5fA8HdnB211zCiiUGLSrHKtGsisOHjDNF OUyc5WIPxvf5LHiKe8452m9X41k2o38DyEJNpsR6KTSW5+F60SZdjCuDDOMVFvXONBLf dw5pCGFPEntXc+oOUqcWvnm6VHGKMVFxTvA54=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I'm using a stripped down domU kernel and it's not seeing eth0:

ipconfig: eth0: SIOCGIFINDEX: No such device
ipconfig: no devices to configure

The VM's config is using:

vif = [ 'model=ioemu' ]

Presumably it's because I've taken out the NIC driver it's using. How do I find out which one it needs (without the dreaded binary search method)?

IOW, what kernel CONFIG_XXX option maps to the ioemu driver?
e1000? OR?

Is this documented somewhere?

Thanks in advance.

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.