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


[Xen-users] NAT routing + HVM DomU's

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] NAT routing + HVM DomU's
From: Steve Copous <jaofos@xxxxxxxxx>
Date: Tue, 19 May 2009 13:25:24 -0500
Delivery-date: Tue, 19 May 2009 11:26:10 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=/vhFg8FosCfmiCqStJOIapNCerJXQlgqwVhqfN078U0=; b=rVVt31MEgybxIwhdOWgFhM5GBRuRvGKZWhWnkL2fq+wBAcw9e6qWD0I57pgebjmfQc thnLpEAe5/vGvRFrv2PW8CiDz3eyaA9Qo5nzOEV3XcZF2T9MVWLtCVd8B4SYakzsy/b9 m69TwfmeNWcaZBjBk6HdJuM69bBhVGytuu3AY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=wsY6Rl/BI+9jj3YN5MJAwoY/19ZztPF3c9L3vWcsNbsnC/WpY8JvfOMJmxefNbLrtw IjaxefCqQ7zXCPcNzP5RYHY7qjD50cxAXQyaSMFH8rBsim4LFoVQtEoODgr2gcSnvArY +ik4pIC7KZKYmPAtT2WZwZYo4dM08Rm4hI3a8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I am attempting to setup a Xen environment hosting several internal
web apps (mostly Ruby on Rails).  I will have an OpenSuse 11 Dom0 with
Ubuntu 9.04 (server) DomU's.  I am only given one IP address for my
server, and none of the DomU's will need to be reachable directly, as
Apache will be handling the proxy load between apps on the DomU's.
What I need is for the Dom0 and all DomU's to be able to communicate
and for the DomU's to be able to communcate with the internet via
routing through Dom0.

However, the issue I appear to be running into, is that running the
DomU's HVM are attempting to communicate via the tapX device instead
of the vifX devices.

Here is a sample of my configurations:

ifconfig on dom0

eth0      Link encap:Ethernet  HWaddr 00:23:7D:51:19:3E
          inet addr:  Bcast:  Mask:

vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet addr:  Bcast:  Mask:

vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet addr:  Bcast:  Mask:

route -n on dom0

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface UH    0      0        0 vif1.0 UH    0      0        0 vif2.0   U     0      0        0 eth0     U     0      0        0 eth0       U     0      0        0 lo         UG    0      0        0 eth0

Relevant configuration information for VM's:

vif=[ 'mac=00:16:3E:C2:AA:XX' ]

I am using dnsmasq to offer DHCP to the DomU's as per the setup
documented here:

I have also tried a static networking setup passing ip=x.x.x.x on the
vif line in the DomU configuration.

Reading through the archives I've seen a couple things mentioning
documented issued with routing in HVM DomU's, but nothing recently
(3.3+).  Has anything changed, or are there any special considerations
when dealing with this type environment?

Any help is much appreciated.


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>