Search results

Yes, I tried disabling gro\gso on eth0 and vmbr0 simultaneously. https://bugzilla.proxmox.com/show_bug.cgi?id=329

# ethtool -K eth0 gro off - same problem

My syslog don't have messages like skb_warn_bad_offload guest 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux - same problem

Debian 6.0.6

pve-kernel-2.6.32-13-pve with same virtual environment works without any warnings or other problems

No effect. I also tried disabling tso (ethtool -K eth0 tso off)

I just upgraded to pvetest Appears to be stable, the kernel panic is not repeated, but the network load in guests OS, syslog the host system clogged messages 10 minutes syslog up to 400 MB!!! The load on the network directly on the host system does not cause problems!

Thanks for you reply This options does not solve the problem with kernel panic May be useful later

I tried to compile the driver from source - no effect

IBM BladeCenter HS22 -[7870H2G]- After kernel version pve-kernel-2.6.32-13-pve kernel panic after any network activity (e.q. upload iso image) pve-kernel-2.6.32-11-pve - works fine pve-kernel-2.6.32-12-pve - works fine pve-kernel-2.6.32-13-pve - works fine pve-kernel-2.6.32-14-pve - kernel...

I am trying to configure a cluster on the two blades IBM BladeCenter cluster.conf.new <?xml version="1.0"?> <cluster config_version="5" name="tlc"> <cman expected_votes="1" keyfile="/var/lib/pve-cluster/corosync.authkey"/> <fencedevices> <fencedevice agent="fence_bladecenter"...