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

Re: [Xen-users] nic naming

  • To: Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • 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
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.