[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Could not get the network to run
Am Dienstag, den 21.06.2005, 14:45 +0000 schrieb Friedmund Lassmann > I've tried to compile/install the xen-unstable-src.tgz from today > and it works fine (at least xend start) but I can not start the network, > not even for Domain-0! I'm using the Broadcom Corporation NetXtreme > BCM5782 Gigabit Ethernet controller. > (I've recompiled the xen kernel after the 'make world' to get the > smbfs module, Did you also configure the kernel to build the module for that broadcom NIC? > but I don't think the kernel is bad since it works fine > if I start it outside from xen) What do you mean with "start a kernel outside from xen"? > What could I try next? > > My settings are: > > manxmaus:~ # ifconfig > eth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST NOARP 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) > Interrupt:17 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:27567 errors:0 dropped:0 overruns:0 frame:0 > TX packets:27567 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:4477653 (4.2 Mb) TX bytes:4477653 (4.2 Mb) > > veth0 Link encap:Ethernet HWaddr 00:30:6E:B0:B8:08 > inet addr:15.136.125.167 Bcast:15.136.127.255 Mask:255.255.248.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:131 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:6275 (6.1 Kb) > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:130 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:6185 (6.0 Kb) TX bytes:0 (0.0 b) > > manxmaus:~ # route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 15.136.120.0 0.0.0.0 255.255.248.0 U 0 0 0 veth0 > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 veth0 > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo > 0.0.0.0 15.136.127.254 0.0.0.0 UG 0 0 0 veth0 > > manxmaus:~ # brctl show > bridge name bridge id STP enabled interfaces > xen-br0 8000.feffffffffff no vif0.0 > eth0 This veth0 is only good for intra-domain networking. It won't help you communicating with the outside world. Configure xen-br0 instead (you broadcom is probably eth0, belonging to that bridge) like you did with veth0 before, and UP it. ip addr del 15.136.125.167/21 dev veth0 ip link set veth0 down ip addr add 15.136.125.167/21 dev xen-br0 ip link set xen-br0 up ip route add default via 15.136.127.254 /nils. > end of dmesg output: > > device vif0.0 entered promiscuous mode > xen-br0: port 1(vif0.0) entering learning state > xen-br0: topology change detected, propagating > xen-br0: port 1(vif0.0) entering forwarding state > bridge: can't decode speed from eth0: 65535 > device eth0 entered promiscuous mode _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |