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

[Xen-users] the tapN network interface


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Zu <zuzhihui@xxxxxxxxx>
  • Date: Wed, 29 Oct 2008 15:10:08 +0800
  • Delivery-date: Wed, 29 Oct 2008 00:10:54 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=nkuxptS052Ah39NzQYXqNzwqsWOsOeSzO0I5CJfq35ATEtlTPZQD9jHLEmvtCAfMaL N1CP/8ztI5EVPU3G+wDej7IVG9Oy5pcb4cqmqC5Ggt6iFITYokjX84iyIxndZUFbBdA/ 2ffMYLdNBOElwDKz4xwAEqpCjNOTe31L10uoc=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,

In domU's config file, I specify the name of the network interfaces, like:

vif = [ 'vifname=x17.162, mac=00:16:3E:00:01:62,bridge=xenbr0' ]

When I create a PVM domU, the interface name is right.

When I create a HVM domU, there will be a additional network interface
named "tapN".  How to know tap0 related to which domU?  Or how to
avoid the tapN interfaces like PVM? I use mrtg to monitor domU's
network usage.

Xen version is 3.2.1

Thanks!

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

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