This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] nic naming

To: Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] nic naming
From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Date: Sun, 28 Jun 2009 23:24:34 +0700
Delivery-date: Sun, 28 Jun 2009 09:25:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1246193469.3943.218.camel@pluto>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1246193469.3943.218.camel@pluto>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Sun, Jun 28, 2009 at 7:51 PM, Goran<xen-list@xxxxxxxx> wrote:
> xm create domU_b => tap0 created in dom0
> xm create domU_a => tap1 created in dom0
> As you can see, the tap devices swapped their names. What should be done
> to avoid this naming convention?

That's the thing with tap. The bad news, there's no method that I know
of that can easily make HVM domU's tap names "persistent". The good
news, depending on how you use domU, that might not matter. You see,
if you use PV drivers (like GPLPV for Windows domU) traffic will go
through the vif. And you can change vif name easily. Try "xm create
--help_config | grep vif"


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>