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

[Xen-devel] Q on vif interface creation


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: ravi kerur <rkerur@xxxxxxxxx>
  • Date: Sun, 20 Dec 2009 21:06:45 -0800
  • Delivery-date: Sun, 20 Dec 2009 21:07:07 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=HEpjj2+wcf44Hiwq7KgRDlsKW6pxLzmEtYAJt8VgJZ/83VURTvbQfANmzpWVvgeWJ1 nrdhDuO7esx4/1577lOE+6LgpjbeNQZaIlT0A2fQRUiIXKhz0rGBzL3Wev5hjb1EQosw vxxOa6z+lynWALfJI3GOK6s2xe5f/BsaGqzpw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hello,

Need inputs on creating "vif" interface with a different name i.e when a domU is installed, vif<dom-id>:<intf-num> is created by default in dom0 and domU which then triggers xenbus state-machine and communication is established. We want to change the name to be  "ncr<dom-id>:<intf-num>", the reason being, we are developing our driver specific netfront and netback which will monitor "ncr" to trigger xenbus state-machine. I am not sure where to start in-order to make these changes. Inputs will be very much appreciated.

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

 


Rackspace

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