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

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


  • To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Jim Fehlig <jfehlig@xxxxxxxxxx>
  • From: "Fischer, Anna" <anna.fischer@xxxxxx>
  • Date: Fri, 16 Oct 2009 04:54:30 +0000
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 15 Oct 2009 21:56:56 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcpM/KOBHkFl4hyHRSOtfUDe+kUQhgBG9irQ
  • Thread-topic: [Xen-devel] static vif/tap names

> Subject: Re: [Xen-devel] static vif/tap names
> 
> Keir Fraser wrote:
> > 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.
> >
> 
> Thanks.  Patch attached.
> 
> Regards,
> Jim
> 
> 
>     Signed-off-by: Jim Fehlig <jfehlig@xxxxxxxxxx>

Much better than the current solution.

Acked-by: Anna Fischer <anna.fischer@xxxxxx>

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