I have received user requests for static vif/tap names. The use case is certainly valid: dom0 tools require consistent and predefined names of virtual network interfaces. The Xen vifname parameter satisfies this use case for pv vifs, but emulated vifs are named dynamically, e.g. tapX.Y. My initial thought was to honor the vifname parameter when generating the qemu args, but there are cases when both pv and emulated vifs are created - e.g. when vif config contains no ''type='' param or when ''type=ioemu''. Two options I have considered are: 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? Regards, Jim _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 14/10/2009 06:30, "Jim Fehlig" <jfehlig@novell.com> 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@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser wrote:> On 14/10/2009 06:30, "Jim Fehlig" <jfehlig@novell.com> 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@novell.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> Subject: Re: [Xen-devel] static vif/tap names > > Keir Fraser wrote: > > On 14/10/2009 06:30, "Jim Fehlig" <jfehlig@novell.com> 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@novell.com>Much better than the current solution. Acked-by: Anna Fischer <anna.fischer@hp.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel