Re: xennet0 not connected

[Jean-Yves Migeon <jeanyves.migeon%free.fr@localhost>]

On 21.09.2010 20:17, Pierre-Philipp Braun wrote:
> # xm network-list bsd -l
> (0
>     ((mac 00:16:3e:1d:66:64)
>         (handle 0)
>         (protocol x86_64-abi)
>         (backend-id 0)
>         (state 4)
>         (backend /local/domain/0/backend/vif/15/0)
>         (tx-ring-ref 510)
>         (rx-ring-ref 509)
>         (feature-rx-notify 1)
>         (event-channel 6)
[snip]
> sit0      Link encap:UNSPEC  HWaddr
> 00-00-00-00-30-00-00-00-00-00-00-00-00-00-00-00
>           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)
[...]
> vif14.0   Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
[...]
> vif15.0   Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff

Nothing suspicious here, except that you have two vif on the same bridge
with two identical MAC. Not really sure if it will work correctly, nor
if it is the correct behavior under Linux.

If you turn off the domU of vif14 (or remove vif14 from the bridge),
does it change anything?

> # tcpdump -i vif15.0 -vv
> tcpdump: WARNING: vif15.0: no IPv4 address assigned
> tcpdump: listening on vif15.0, link-type EN10MB (Ethernet), capture size
> 96 bytes
> 
> It seems nothing comes out of the domU.

When pinging, do you see any activity regarding xennet event channel?
vmstat -i will show that.

-- 
Jean-Yves Migeon
jeanyves.migeon%free.fr@localhost