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

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



On Wed, May 20, 2009 at 1:25 AM, Steve Copous <jaofos@xxxxxxxxx> wrote:
> 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.

Correct.

>
> Here is a sample of my configurations:
>
> ifconfig on dom0
>
> eth0      Link encap:Ethernet  HWaddr 00:23:7D:51:19:3E
>           inet addr:172.26.6.17  Bcast:172.26.7.255  Mask:255.255.254.0
>
> vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet addr:10.0.2.128  Bcast:0.0.0.0  Mask:255.255.255.255
>
> vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet addr:10.0.1.128  Bcast:0.0.0.0  Mask:255.255.255.255
>

So I assume you use network-route and vif-route scripts or its variant?
You have two options :
- install PV drivers for HVM domU so traffic can go through vif. AFAIK
none is available for the default Ubuntu kernel, so the easiest way si
actually to convert your Ubuntu HVM to PV.
- use bridging setup, and setup NAT with iptables. This is what
libvirtd does, giving NATed address 192.168.122.0/24

-- 
Fajar

_______________________________________________
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®.