|
|
|
|
|
|
|
|
|
|
xen-users
[Xen-users] cannot ping after xen install
I installed 3.2 on a Ubuntu gutsy (7.10 / AMD64) server and everything
looks fine. Xen booting up without errors or warnings but ping fails
when I try to ping a machine in my network. 8 pings are OK but the ninth
hangs for about 3000ms, the next 8 or 10 pings are normal and so on..
The dom0 itself is in that time not pingable from network. Well, that's
not all... I just have to wait long enough (about 10 min.) and sometimes
a miracle happen and everything works...
### did I overlook something here?
---------------------------------------------------------------------
cd /usr/src && wget
http://bits.xensource.com/oss-xen/release/3.2.0/xen-3.2.0.tar.gz
tar -xzf xen-3.2.0.tar.gz && cd xen-3.2.0
hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg
make all && make install
update-rc.d xend defaults 20 21
update-rc.d xendomains defaults 21 20
depmod 2.6.18.8-xen
mkinitramfs -o /boot/initrd.img-2.6.18.8-xen 2.6.18.8-xen
update-grub
### /etc/xen/xend-config.sxp
(network-script network-bridge)
(vif-script vif-bridge)
### /etc/modules
loop max_loop=64
reboot
---------------------------------------------------------------------
### brctlshow:
---------------------------------------------------------------------
bridge name bridge id STP enabled interfaces
eth0 8000.00304893a8b4 no peth0
---------------------------------------------------------------------
### ifconfig -a:
---------------------------------------------------------------------
eth0 Link encap:Ethernet HWaddr 00:30:48:93:A8:B4
inet addr:192.168.2.50 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::230:48ff:fe93:a8b4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1791 errors:0 dropped:0 overruns:0 frame:0
TX packets:1581 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:188671 (184.2 KB) TX bytes:151714 (148.1 KB)
eth1 Link encap:Ethernet HWaddr 00:30:48:93:A8:B5
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)
Base address:0x2020 Memory:df260000-df280000
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:30:48:93:A8:B4
inet6 addr: fe80::230:48ff:fe93:a8b4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3196 errors:0 dropped:0 overruns:0 frame:0
TX packets:1581 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:311129 (303.8 KB) TX bytes:159256 (155.5 KB)
Base address:0x2000 Memory:df220000-df240000
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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)
---------------------------------------------------------------------
### /etc/network/interfaces
---------------------------------------------------------------------
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.2.50
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255
gateway 192.168.2.1
# dns-* options are implemented by the resolvconf package, if...
dns-nameservers 192.168.2.1
### DO I NEED THIS ??????
post-up echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp
---------------------------------------------------------------------
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-users] cannot ping after xen install,
Zoran Kikic <=
|
|
|
|
|