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

Re: [Xen-devel] [Xen-users] xl and vifname


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
  • Date: Wed, 28 Dec 2011 15:37:58 +0000
  • Delivery-date: Wed, 28 Dec 2011 15:38:32 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Openpgp: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc

Hi Wei,

On Wed, Dec 28, 2011 at 03:25:57PM +0000, Wei Liu wrote:
> Does xm serve your purpose -- specifying dom0 network interface of a
> given name (rather then using vifX.X)?

Yes. We need to statically configure the vif names in order to have
them be the same every time, and to know which virtual machine
configuration they belong to. Not have them change every time the VM
is restarted.

(Yes I am aware that it would be possible to translate the vifX.Y
string into a domU name and go from there, but that adds a lot of
complexity)

> If it can serve you purpose, can you verify which network backend you
> are using by running following command:
> 
> $ ps aux | egrep '(qemu|net)'

This didn't match anything. These are PV domUs and there isn't a
process in dom0 for each domU's netback. This is 4.0.1 on Debian
stable.

> If you're running netback and you can use you preferred name for the
> interface, then a similar fix for xl should be possible.

Something like:

    vif = [ "mac=00:16:3e:8e:ac:0a, ip=192.168.82.198, vifname=vm-85" ]

has worked for us for ~5 years through Xen 3.x and 4.x.

Cheers,
Andy

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


 


Rackspace

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