Re: [Xen-users] Fully virtualized networking issues.

[Reto Gantenbein <reto.gantenbein@xxxxxxxxxxx>]

Hi

I did try again with another network bridge that throughout uses  
standard MTU 1500. Also here I cannot get any packet in domU and vice  
versa.
domU-hvm  --b---         74    0.0    1056640   12.6    1064960       
12.7     1    2        0        0    2        0        0        0  
2149620944
Net0 RX:        0bytes        0pkts        0err   458296drop   
TX:        0bytes        0pkts        0err         
0drop                                                <-- bridge that  
uses MTU 5000
Net1 RX:        0bytes        0pkts        0err    34121drop   
TX:        0bytes        0pkts        0err         
0drop                                                 <-- bridge that  
uses MTU 1500
When I try to ping a host from domU these packets just get lost. No  
errors or drops at domU network interface but also no appearance of  
these packets in domU network.
It really seems that there is no connectivity at all between dom0  
networking and the emulated domU device. What could cause this?
Kind regards
Reto Gantenbein



On May 2, 2008, at 12:14 PM, Reto Gantenbein wrote:

> Hello everybody
>
> I experience the same problem with a fully virtualized linux domU on  
> xen-3.2.0. The machine is a Sun X4200M2 with a "nVidia Corporation  
> CK804 Ethernet Controller" network device. It's a gigabit device  
> using the forcedeth driver. The tap device works fine but then the  
> vif drops all the packets! Why is this?
> Here my output:
>
> bridge name     bridge id               STP enabled     interfaces
> core            8000.00144f9ac773       no              pcore
>                                                        vif8.1
>                                                         vif17.0
>                                                         tap0
>
> pcore     Link encap:Ethernet  HWaddr 00:14:4F:xx:xx:xx
>          UP BROADCAST RUNNING MULTICAST  MTU:5000  Metric:1
>          RX packets:75480611 errors:4 dropped:0 overruns:0 frame:4
>          TX packets:71130077 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:139163029640 (132716.2 Mb)  TX bytes:162640218550  
> (155105.7 Mb)
>          Interrupt:47 Base address:0x8000
>
> vif8.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>          UP BROADCAST RUNNING MULTICAST  MTU:5000  Metric:1
>          RX packets:59547485 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:62527763 errors:0 dropped:915 overruns:0 carrier:0
>          collisions:0 txqueuelen:32
>          RX bytes:131652168382 (125553.2 Mb)  TX bytes:134094016346  
> (127882.0 Mb)
> vif17.0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:0 errors:0 dropped:177716 overruns:0 carrier:0
>          collisions:0 txqueuelen:32
>          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>
> tap0      Link encap:Ethernet  HWaddr 00:FF:90:57:73:FD
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:173199 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:500
>          RX bytes:0 (0.0 b)  TX bytes:20296723 (19.3 Mb)
>
>
> I can see the interface in my domU but it doesn't receive any  
> traffic at all. I already tried with model=ne2k_pci and  
> model=rtl8139 in the domU configuration. It didn't change anything.
> I also have to mention that the bridged interface pcore is using MTU  
> 5000 (that cannot be changed because the other domU relies on it).  
> When I would like to assign MTU 5000 to vif17.0 it fails with a  
> "SIOCSIFMTU: Invalid argument" errno.
> Any hints about this?
>
> Kind regards,
> Reto Gantenbein
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

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