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.
http://www.howtoforge.com/forums/showthread.php?t=39923
Is there anyone who has any other solution??
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Tue, Dec 22, 2009 at 8:57 PM, 박은병 <peb1611@gmail.com> wrote:> #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> # 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> and my domU configuration file> vif = [ ''bridge=eth0'' ] > ip = "192.168.0.101" > netmask= "255.255.255.0" > gateway = "192.168.0.1"> I can found similar problem on internet, but I don''t understand why does > hoster''s bridged setup is problematic.First of all, are you using bridged setup or routed setup? If you use bridge, you wouldn''t need to specify ip, netmask, or gateway on domU config file. Also, if using bridges setup, dom0 bridge IP address (in your case it''s called eth0) should be on the same segment as domU''s network interface. You''re using two different segments. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> On Tue, Dec 22, 2009 at 8:57 PM, 박은병<peb1611@gmail.com> wrote: > >> #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 >> > >> # 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 >> > >> and my domU configuration file >> > >> vif = [ ''bridge=eth0'' ] >> ip = "192.168.0.101" >> netmask= "255.255.255.0" >> gateway = "192.168.0.1" >> > >> I can found similar problem on internet, but I don''t understand why does >> hoster''s bridged setup is problematic. >> > >I don''t know if this matters but the if config show 192.168.1.x and the config file shows 192.168.0.x _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
As Fajar said that for a bridged connection you don''t need ip settings inside domU config. As in communication takes place using Mac addresses. So you just need simply to access your domU GUI using VNC. Login as root go to System -> Administration ->Network -> double click your eth0 (inactive)-> inside Hardware device tab change your mac by clicking probe. Note down the new mac and write the same new one inside domU config file to avoid further inconvenience. Like this vif = [ ''mac= 00:xx:xx:xx, bridge=eth0'' ] Regards, Fasiha Ashraf --- On Wed, 23/12/09, Fajar A. Nugraha <fajar@fajar.net> wrote: From: Fajar A. Nugraha <fajar@fajar.net> Subject: Re: [Xen-users] xen network problen domU To: "박은병" <peb1611@gmail.com> Cc: xen-users@lists.xensource.com Date: Wednesday, 23 December, 2009, 6:39 AM On Tue, Dec 22, 2009 at 8:57 PM, 박은병 <peb1611@gmail.com> wrote:> #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> # 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> and my domU configuration file> vif = [ ''bridge=eth0'' ] > ip = "192.168.0.101" > netmask= "255.255.255.0" > gateway = "192.168.0.1"> I can found similar problem on internet, but I don''t understand why does > hoster''s bridged setup is problematic.First of all, are you using bridged setup or routed setup? If you use bridge, you wouldn''t need to specify ip, netmask, or gateway on domU config file. Also, if using bridges setup, dom0 bridge IP address (in your case it''s called eth0) should be on the same segment as domU''s network interface. You''re using two different segments. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Remember doing service network restart after saving changes to eth0 interface Regards, Fasiha Ashraf As Fajar said that for a bridged connection you don''t need ip settings inside domU config. As in communication takes place using Mac addresses. So you just need simply to access your domU GUI using VNC. Login as root go to System -> Administration ->Network -> double click your eth0 (inactive)-> inside Hardware device tab change your mac by clicking probe. Note down the new mac and write the same new one inside domU config file to avoid further inconvenience. Like this vif = [ ''mac= 00:xx:xx:xx, bridge=eth0'' ] Regards, Fasiha Ashraf --- On Wed, 23/12/09, Fajar A. Nugraha <fajar@fajar.net> wrote: From: Fajar A. Nugraha <fajar@fajar.net> Subject: Re: [Xen-users] xen network problen domU To: "박은병" <peb1611@gmail.com> Cc: xen-users@lists.xensource.com Date: Wednesday, 23 December, 2009, 6:39 AM On Tue, Dec 22, 2009 at 8:57 PM, 박은병 <peb1611@gmail.com> wrote:> #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> # 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> and my domU configuration file> vif = [ ''bridge=eth0'' ] >ip = "192.168.0.101"> netmask= "255.255.255.0" > gateway = "192.168.0.1"> I can found similar problem on internet, but I don''t understand why does > hoster''s bridged setup is problematic.First of all, are you using bridged setup or routed setup? If you use bridge, you wouldn''t need to specify ip, netmask, or gateway on domU config file. Also, if using bridges setup, dom0 bridge IP address (in your case it''s called eth0) should be on the same segment as domU''s network interface. You''re using two different segments. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users