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: "Max E. Baro" <MEB@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] domU HVM network problem
From: Carles Pina i Estany <carles@xxxxxxxx>
Date: Mon, 10 Mar 2008 09:38:08 +0100
Cc: "'xen-users@xxxxxxxxxxxxxxxxxxx'" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 10 Mar 2008 01:38:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <51D1F0F52CF63A4689328DDC077F7498A1D031@xxxxxxxxxxxxxxxxxxxxxxxx>
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: <51D1F0F52CF63A4689328DDC077F7498A1D031@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.17 (2007-11-01)
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?

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