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

Re: [Xen-users] xen domU ID and static routing

To: Pasi KÃrkkÃinen <pasik@xxxxxx>
From: Peter Viskup <skupko.sk@xxxxxxxxx>
Date: Tue, 05 Jan 2010 21:11:22 +0100
Cc: Info - csdemmer <info@xxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 05 Jan 2010 12:12:20 -0800
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=au55ru3MHDlYvTbck9wS7h7XH5pAgVvRvfMy5JTGlE5F5exNqU1EW/0iJ96cMVRm+J WoArrfi1xDn2sACP6DghADtq2CdvaesmChfT65KXO3PloggzVTOWuGcigNP/T+jG58xC WAwYdm6ciavMZpiF/DFN26MNxkUyGrar8lbOo=
List-id: Xen user discussion <xen-users.lists.xensource.com>

Pasi KÃrkkÃinen wrote:

Another option is to parse the guest ID from for example "xm list" and
use that in your firewall script to create the vif name.

I will recommend Xen commands for that.
Like this:

# for dev in $(xm network-list <xen-vhost> | awk '/^[0-9]+/ {print$9}'); do xenstore-read $dev/vifname; done


But it is much easier to use the vifname configuration option...

--
Peter Viskup

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

References:
- [Xen-users] xen domU ID and static routing
  - From: Info - csdemmer
- Re: [Xen-users] xen domU ID and static routing
  - From: Pasi Kärkkäinen

Prev by Date: Re: [Xen-users] Existing windows server to XEN howto?
Next by Date: [Xen-users] pv_ops dom0 kernel: /proc/cpuinfo shows 0.000 MHz
Previous by thread: Re: [Xen-users] xen domU ID and static routing
Next by thread: Re: [Xen-users] xen domU ID and static routing
Index(es):
- Date
- Thread

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