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

[Xen-users] xen network problen domU

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xen network problen domU
From: 박은병 <peb1611@xxxxxxxxx>
Date: Tue, 22 Dec 2009 22:57:30 +0900
Delivery-date: Tue, 22 Dec 2009 05:58:53 -0800
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; bh=5eiWtwUxkXX4mUlCNdTeJbDGK6ZVk/rpcYAtFk8bO4E=; b=F0RbciRkHD1q8eDEGkRi0ALt+BpZB0YQ6KKR56us1yEkt/k16EcN+zKtf96sOUMb4g WU3wbSI75wOvkUmIrhd9+6cq7tqx7ReNtVVvIq/4svbC2HPNyjUwEuOP3/Qx9UU3lwJz 0Be7xnltOWEwmk8TgbsGbDH668YuWe/MTcxTw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hsYxx7S+Rj8da0aY40H/GkvH/1jYl60A0dLMJ8HSIu572+TCk0hZyaj1IJ0/Xk0rEX vt27qt7svi34vaSAqWXHg8Pzo9EJMrVYCMt9O4uKGoJK4n//Qhx576tqG1g/nbSqS41+ 0a28Ihu0UmPKZ1tCYU0qyW9j+/W2X2vrZW/0Q=
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've just installed ubuntu 9.10 karmic server i386 on my mac mini machine
xen 3.4.2, dom0 is Jeremy's pvops kernel 2.6.31.6 and domU is vanila kernel 2.6.32.
dom0 and domU are ubuntu 9.10 server distribution rootfile system.
 
The dom0 can connect internet. but DomU has no network connections.
 
I've tried to ping, arping, tcpdump
 
ping from domU to dom0
 
# ping 147.46.125.xx
PING 147.46.125.xx (147.46.125.xx) 56(84) bytes of data.
^C
--- 147.46.125.xx ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1007ms
 
at the same time, tcpdump on dom0 show up the ICMP request by domU
 
# arping 147.46.125.xx (from domU to dom0)
ARPING 147.46.125.xx from 192.168.1.101 eth0
Unicast reply from 147.46.125.xx [00:16:CB:A5:DD:66]  0.646ms
Unicast reply from 147.46.125.xx [00:16:CB:A5:DD:66]  0.583ms
Unicast reply from 147.46.125.xx [00:16:CB:A5:DD:66]  0.589ms
Unicast reply from 147.46.125.xx [00:16:CB:A5:DD:66]  0.583ms
Unicast reply from 147.46.125.xx [00:16:CB:A5:DD:66]  0.581ms
Unicast reply from 147.46.125.xx [00:16:CB:A5:DD:66]  0.581ms
Unicast reply from 147.46.125.xx [00:16:CB:A5:DD:66]  0.586ms
 
at the same time, tcpdump on dom0 show up the ARP request by domU
 
#ping from dom0 to domU
# ping 192.168.101.1
PING 192.168.101.1 (192.168.101.1) 56(84) bytes of data.
^C
--- 192.168.101.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3022ms
 
but ping cannot get the response from dom0 to domU, vice versa as well.
 
what is the problem??
 
#ifconfig -a (dom0)
eth0      Link encap:Ethernet  HWaddr 00:16:cb:a5:dd:66 
          inet addr:147.46.125.xx Bcast:147.46.125.255  Mask:255.255.255.0
          inet6 addr: fe80::216:cbff:fea5:dd66/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:61737 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1024 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5299205 (5.2 MB)  TX bytes:252992 (252.9 KB)
lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  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)
peth0     Link encap:Ethernet  HWaddr 00:16:cb:a5:dd:66 
          inet6 addr: fe80::216:cbff:fea5:dd66/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:64736 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1079 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6453075 (6.4 MB)  TX bytes:257494 (257.4 KB)
          Interrupt:16
vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff 
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:36 errors:0 dropped:0 overruns:0 frame:0
          TX packets:62408 errors:0 dropped:240 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:2602 (2.6 KB)  TX bytes:6237639 (6.2 MB)
wlan0     Link encap:Ethernet  HWaddr 00:14:51:ed:fa:c3 
          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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
wmaster0  Link encap:UNSPEC  HWaddr 00-14-51-ED-FA-C3-00-00-00-00-00-00-00-00-00-00 
          [NO FLAGS]  MTU:0  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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
 
# ifconfig -a (domU)
eth0      Link encap:Ethernet  HWaddr 00:16:3e:1f:4f:46 
          inet addr:192.168.1.101  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::216:3eff:fe1f:4f46/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:77419 errors:0 dropped:0 overruns:0 frame:0
          TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6665565 (6.6 MB)  TX bytes:4439 (4.4 KB)
          Interrupt:10
lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:168 (168.0 B)  TX bytes:168 (168.0 B)
 
and my domU configuration file
 
      kernel = "/boot/vmlinuz-2.6.32-domU"
      ramdisk = "/boot/initrd.img-2.6.32-domU"
      memory = 512
      name = "ubuntu1"
      vif = [ 'bridge=eth0' ]
      ip = "192.168.0.101"
      netmask= "255.255.255.0"
      gateway = "192.168.0.1"
      disk =[ 'file:/root/xen/domainU/ubuntu1/ubuntu1.img,xvda1,w',
      'file:/root/xen/domainU/ub      untu1/ubuntu1_swap.img,xvda2,w' ]
      hostname= "ubuntu1"
      root = "/dev/xvda1 ro"extra = "console=hvc0 earlyprintk=xen"
I can found similar problem on internet, but I don't understand why does hoster's bridged setup is problematic.
 
Is there anyone who has any other solution??
 
 
 
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>