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

Re: [Xen-devel] static vif/tap names


  • To: Jim Fehlig <jfehlig@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Wed, 14 Oct 2009 07:48:54 +0100
  • Cc:
  • Delivery-date: Tue, 13 Oct 2009 23:49:22 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcpMj3t9vJP6lsk/STaTerw3Vjr+eQACum26
  • Thread-topic: [Xen-devel] static vif/tap names

On 14/10/2009 06:30, "Jim Fehlig" <jfehlig@xxxxxxxxxx> wrote:

> 1. Appending vifname, if specified, to "tap" (tap-<vifname>), otherwise
> use current dynamic tapX.Y
> 2. Add a 'tapname=' parameter to vif config.  This would allow
> controlling the vif and tap interface names independently.
> 
> Is once of these solutions acceptable?  Any alternate suggestions?

Option (1) sounds nice and straightforward.

 -- Keir



_______________________________________________
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®.