From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jim Fehlig <jfehlig@novell.com>
Subject: static vif/tap names
Date: Tue, 13 Oct 2009 23:30:15 -0600
Message-ID: <4AD561E7.3090808@novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

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