Xen project Mailing List

On 8/17/07, Bart Verwilst <lists@xxxxxxxxxxx> wrote:

Hi,

This post really made my day, as i'm having the same problem myself.
Thanks for writing out the problem so clearly! I'm using the same kernel, and have been looking for an answer since yesterday myself.
Could you please let us know whether the ethtool trick works?
I'll try it as well as soon as i'm home in an hour or so, and let you guys know of the outcome!

Thanks!

Kind regards,

Bart Verwilst

----- Original Message -----
From: "Hinrich Aue" <hinrich.aue@xxxxxxxxxxxxxxxx>
To: "Emre Erenoglu" < erenoglu@xxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Sent: Friday, August 17, 2007 2:16:56 PM (GMT+0100) Europe/Berlin
Subject: AW: [Xen-users] Gutsy Xen 3.1 2.6.22-9-xen network-bridge problem

Yes. I thought that's in the link?

Whatever, use that command ethtool - K eth0 tx off on your interfaces (on
dom0).

I don't know if that is necessary, but I use it on every interface /
bridges.

You can put that command into the xen networking scripts. Don't know exactly
where.

Hinrich

_____

Von: Emre Erenoglu [mailto:erenoglu@xxxxxxxxx ]
Gesendet: Freitag, 17. August 2007 14:05
An: Hinrich Aue
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Betreff: Re: [Xen-users] Gutsy Xen 3.1 2.6.22-9-xen network-bridge problem

Hi Hinrich,

So do you think it's because of this checksum offloading? What shall I do to
get rid of it? Couldn't understand from the message...

would "ethtool - K eth0 tx off" be the right command?

Thanks for your interest and Best regards,

Emre

On 8/17/07, Hinrich Aue <hinrich.aue@xxxxxxxxxxxxxxxx> wrote:

I had the same problem. It's a checksum problem I guess. (was in my case)

http://lists.xensource.com/archives/html/xen-users/2006-05/msg00817.html

this might help (hopefully)

_____

Von: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx ] Im Auftrag von Emre Erenoglu
Gesendet: Freitag, 17. August 2007 12:11
An: xen-users@xxxxxxxxxxxxxxxxxxx
Betreff: [Xen-users] Gutsy Xen 3.1 2.6.22-9-xen network-bridge problem

Hi,

I have a strange problem with my networking setup. I read all forums around
the world where people had similar problems, but couldn't find a solution.

I have an Attansic L1 gigeth chip on my mainboard. This chip works OK in
stock Ubuntu Gutsy (development) 2.6.22-9-generic kernel.

When I boot into Xen, and after the bridge is created, the network stops
working. Some info:

- If I do " /etc/xen/scripts/network-bridge stop "  then the network comes
back...

- I can ping sites, but can never "communicate" with them. For example, I
can "telnet" to 22th port of an sshd server, receive the "welcome to xyz
sshd server etc." but can never send any command. Same for telnet/http/ftp
connections. The system also cannot resolve DNS names, but can still ping.
Same thing happens inside the DomUs.

- My /etc/xen/xend-config.sxp has " (network-script network-bridge) " and "
(vif-script vif-bridge) " directives.

ifconfig -a output:

eth0      Link encap:Ethernet  HWaddr 00:18:F3:9D:6E:FC
         inet addr: 192.168.1.2 <http://192.168.1.2/ >   Bcast:192.168.1.255
<http://192.168.1.255/>   Mask: 255.255.255.0 < http://255.255.255.0/>
         inet6 addr: fe80::218:f3ff:fe9d:6efc/64 Scope:Link
         UP BROADCAST RUNNING  MTU:1500  Metric:1
         RX packets:17016 errors:0 dropped:0 overruns:0 frame:0
         TX packets:20307 errors:0 dropped:0 overruns:0 carrier:1
         collisions:0 txqueuelen:1000
         RX bytes:6377107 (6.0 MB)  TX bytes:9225065 (8.7 MB)

lo        Link encap:Local Loopback
         inet addr: 127.0.0.1 <http://127.0.0.1/>   Mask:255.0.0.0
<http://255.0.0.0/>
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:636 errors:0 dropped:0 overruns:0 frame:0
         TX packets:636 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:11732 (11.4 KB)  TX bytes:11732 ( 11.4 KB)

veth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         BROADCAST NOARP MULTICAST  MTU:1500  Metric:1
         RX packets:18 errors:0 dropped:0 overruns:0 frame:0
         TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:3614 (3.5 KB)  TX bytes:18219 (17.7 KB)

veth1     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
         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:0
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

veth2     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
         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:0
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

veth3     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
         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:0
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         BROADCAST NOARP  MTU:1500  Metric:1
         RX packets:38 errors:0 dropped:0 overruns:0 frame:0
         TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:18219 ( 17.7 KB)  TX bytes:3684 (3.5 KB)

vif0.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         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:0
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

vif0.2    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         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:0
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

vif0.3    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         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:0
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

When I run  "  network-bridge start ", the xenbr0 interface is created,
brctl shows the bridge is created with two interfaces inside. But, network
doesn't work. It seems that I can receive packets but not send.

Syslog shows:

atl1 0000:03:00.0: Unable to enable MSI: -1
atl1 0000:03:00.0: eth0 link is up 100 Mbps full duplex
eth0: no IPv6 routers present
device vif0.0 entered promiscuous mode
audit(1187308448.174:7): dev=vif0.0 prom=256 old_prom=0 auid=4294967295
xenbr0: port 1( vif0.0) entering learning state
atl1 0000:03:00.0: Unable to enable MSI: -1
atl1 0000:03:00.0: peth0 link is up 100 Mbps full duplex
xenbr0: topology change detected, propagating
xenbr0: port 1(vif0.0) entering forwarding state
device peth0 entered promiscuous mode
audit(1187308449.198 :8): dev=peth0 prom=256 old_prom=0 auid=4294967295
xenbr0: port 2(peth0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 2(peth0) entering forwarding state

Do you have any idea what is causing this? I can give more information if
requested. (can't issue the network-bridge start command now as it will
disconnect me from the machine if I do so, I'm remotely connected at the
moment)

P.S. I tried also with a USB ethernet card, same result.

Thanks for any insight,

Best regards,

Emre

--
Emre Erenoglu
erenoglu@xxxxxxxxx  <mailto:erenoglu@xxxxxxxxx>

--
Emre Erenoglu
erenoglu@xxxxxxxxx

!DSPAM:3,46c5920f201951049316272!

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

Re: AW: [Xen-users] Gutsy Xen 3.1 2.6.22-9-xen network-bridge problem