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] Routed dom0 setup problem -- second time around

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Routed dom0 setup problem -- second time around
From: Rich Wales <richw@xxxxxxxxx>
Date: Fri, 28 Dec 2007 17:19:38 -0800
Delivery-date: Fri, 28 Dec 2007 17:20:11 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <477546F5.4080804@xxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <47749EFF.2050408@xxxxxxxxxxxxxxxxxxxx> <4774ACBA.4010800@xxxxxxxxxxxx> <4774ADA1.2080801@xxxxxxxxxxxx> <4774B139.5000004@xxxxxxxxxxxxxxxxxxxx> <4774CA2E.9040809@xxxxxxxxxxxx> <477546F5.4080804@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20071031 Thunderbird/ Mnenhy/
OK, I finally managed to fix my earlier problem (routed configuration
refusing to launch domU's).

The answer turned out to be that if the network interface to be used
by the domU's is anything other than the default "eth0", the interface
name must be explicitly passed (via a netdev= parameter) to vif-route
-- NOT just to network-route.

Here is a xend-config.sxp that appears to work for me now:

(xen-api-server ((unix)))
(xend-http-server yes)
(xend-unix-server yes)
(xend-relocation-server no)
(xend-port 8000)
(xend-address '')
(xend-relocation-hosts-allow '')
(network-script 'network-route netdev=dmz0')
(vif-script 'vif-route netdev=dmz0')
(dom0-min-mem 196)
(dom0-cpus 0)
(vncpasswd '')

Note that my non-default network interface (dmz0) is given as a parameter
to vif-route, as well as to network-route.  This point wasn't mentioned
anywhere in any of the documentation or discussions I could find online,
and I had to trace through the vif-route script, a line at a time, before
finally discovering that the reason it was failing was because it wasn't
able to identify the network interface on its own.

I hope this info can be incorporated into some FAQ's and how-to's, so
that other people won't have to suffer the way I did.

Rich Wales      ===      Palo Alto, CA, USA      ===     richw@xxxxxxxxx
http://www.richw.org   ===   http://en.wikipedia.org/wiki/User:Richwales

Xen-users mailing list