From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Q on netfront/netback driver Date: Mon, 1 Feb 2010 16:16:02 -0500 Message-ID: <20100201211602.GC2756@phenom.dumpdata.com> References: <20100201173714.GA26825@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: ravi kerur Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > In addition, I had follow-up question on creation of "vif" interface(this > is what I was referring to when I mentioned about instantiation of > netfront/netback), if I were to change this "vif" name to something else, > which part of the code should be modified. I have been searching for this You definitly will need to modify the udev rules and potentially a bunch of shell scripts in: xen/tools/hotplug/Linux If you mean the source code of the kernel, look in drivers/xen/netback/* files. .. snip .. > > > However, I do not see the drivers listed when "lsmod" is executed on dom0 > > or > > > domU. > > > > It might be very well compiled in, at which point it is not a module. > > Look in your .config file for NETBACK. Ah, I was incorrect. It is CONFIG_XEN_NETDEV_BACKEND.