WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] domU HVM network problem

To: 'Carles Pina i Estany' <carles@xxxxxxxx>
Subject: RE: [Xen-users] domU HVM network problem
From: "Max E. Baro" <MEB@xxxxxxxxxxxxxxxxx>
Date: Mon, 10 Mar 2008 17:42:47 -0400
Cc: "'xen-users@xxxxxxxxxxxxxxxxxxx'" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 10 Mar 2008 14:43:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I create a bridge in network-route but I don't use it.  I commented out the 'brctl addif' command in /etc/qemu-ifup.  I also did not enable proxy_arp in this configuration.

Verify the routing in your dom0 with 'ip r' and make sure they are correct.  The routes are added by vif-route per interface.  Also, you will need to make sure the default gateway in your domU is pointing to 192.168.10.1.  Can you ping that address from the domU?

In dom0 you should have a route to the domU interface:

192.168.0.0 dev vif0.0  scope link  src 192.168.4.53


Max Baro
Technical Support Supervisor
FACTS Services, Inc.
(305) 284 - 7440
meb@xxxxxxxxxxxxxxxxx



-----Original Message-----
From: Carles Pina i Estany [mailto:carles@xxxxxxxx]
Sent: Monday, March 10, 2008 4:38 AM
To: Max E. Baro
Cc: 'xen-users@xxxxxxxxxxxxxxxxxxx'
Subject: Re: [Xen-users] domU HVM network problem



Hello,

On Mar/09/2008, Max E. Baro wrote:
> By network address I mean in the machine.cfg on the vif= line instead of
> assigning an IP address I use the network address which in TCP/IP end in a
> zero.  This is because the VIF is not actually the tunnel to the domU nic.
> My vif line looks like this:
>
> vif = [ 'type=ioemu, vifname=vif0.0, ip=192.168.0.0, mac=FA:CE:00:00:00:01'

correct, yesterday night I tried (in ip) the same LAN than eth0 in dom0
and Xen was failing to create the machine, now is fine.

> You have to make sure the tuntap module is loaded by typing lsmod:

yes, it's there

> in dom0:
> tap0      Link encap:Ethernet  HWaddr CE:B9:F8:5E:22:D1
>           inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0

same here

> in domU:
> [root@Xdom1 ~]# ip r
> 192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.2
> default via 192.168.0.1 dev eth0

I cannot ping from domU to the 192.168.0.1 :-(

> My dom0 and each of my domU's are all on different subnets so I can
> use dom0 as a router. 
>
> I hope this helps.

192.168.10.150 is my domU IP
192.168.10.1 is my dom0 IP for tap0
192.168.0.1 is my dom0 IP for eth0

If I ping from domU to dom0 I can see "something":
-----------
servidor:/etc/xen/scripts# tcpdump -i tap0
tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
listening on tap0, link-type EN10MB (Ethernet), capture size 96 bytes
09:28:29.965232 arp who-has 192.168.10.1 tell 192.168.10.150
09:28:30.965280 arp who-has 192.168.10.1 tell 192.168.10.150
09:28:31.965310 arp who-has 192.168.10.1 tell 192.168.10.150
09:28:33.965421 arp who-has 192.168.10.1 tell 192.168.10.150
-----------

But not answering.

My dom0 network configuration is:
-------
tap0      Link encap:Ethernet  HWaddr 7E:2D:04:8D:94:CF
          inet addr:192.168.10.1  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: fe80::7c2d:4ff:fe8d:94cf/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:404 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:24848 (24.2 KiB)  TX bytes:972 (972.0 b)

vif38.0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet addr:192.168.10.0  Bcast:192.168.10.255  Mask:255.255.255.255
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

eth0      Link encap:Ethernet  HWaddr 00:1A:A0:D9:D5:CE
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::21a:a0ff:fed9:d5ce/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3515449 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3748272 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1491664039 (1.3 GiB)  TX bytes:3251114826 (3.0 GiB)
          Interrupt:16
-------

(I executed echo 1 > /proc/sys/net/ipv4/conf/tun0/proxy_arp, just in case)

What we have different?


I suspect about that bridge that I did yesterday. Could you show me
your brctl show output? The question is... the bridge xenbr0 has, as
interface, tap0 only? Or has some other interface like eth0?
I would like to test but now it's a remote machine :-)


Thank you for all your help!

--
Carles Pina i Estany            GPG id: 0x8CBDAE64
        http://pinux.info       Manresa - Barcelona

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