Re: [Xen-devel] domU - no networking

[stoeni <xen@xxxxxxxxx>]

keir,

Keir Fraser schrieb:
> The transmit statistic on xen-br0 is a red herring: looking at my
> working system, the xen-br0 interface also reports 0 packets
> transmitted. Odd, but obviously therefore not an indication of trouble.

ok, good to know.

> It sounds like dom0 networking is okay for you. In cases where our
> bridging setup doesn't work, I believe it is usual for networking to
> fail completely (both dom0 and domU).

dom0 networking is fine.

i see a zombie process in the processtable:

USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
root      2188  0.0  0.0     0    0 ?        Z    Oct15   0:00
[network-bridge] <defunct>


> When you boot a domU, do you have a vif called something like 'vif1.1'
> in dom0's ifconfig listing? Does this interface show any packets sent or
> received? 

yes, recieved and transmit packets:

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1708751 errors:0 dropped:0 overruns:0 frame:0
          TX packets:913713 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2540344455 (2.3 GiB)  TX bytes:64017546 (61.0 MiB)

peth0 also has traffic in and out.

> Does 'brctl show' show vif1.1 attached to xen-br0?

yes, it does:

root@xen300 [tmp] # brctl show
bridge name     bridge id               STP enabled     interfaces
xen-br0         8000.feffffffffff       no              peth0
                                                        vif0.0
looking on a 2.0.7 bridge it looks different:

root@xen207 [tmp] # brctl show
bridge name     bridge id               STP enabled     interfaces
xen-br0         8000.00e018526ab6       no              eth0
                                                        vif2.0

maybe problems with this peth0 thing? should the bridge be attachted to
eth0 instead of peth0?

here is some dmesg output from dom0:

e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex
device vif0.0 entered promiscuous mode
bridge: can't decode speed from peth0: 65535
device peth0 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
e1000: peth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex
xen-br0: port 2(peth0) entering learning state
xen-br0: topology change detected, propagating
xen-br0: port 2(peth0) entering forwarding state

the 100mbps link is ok, this machine currently runs in a test environment.

anything else i should look at to track this problem down?


-- 
Tschaw/2,
Stoeni!

++ Please remember: rm -rf means "read mail -really fast" ++

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel