Recent content by olaszfiu

HI Alwin, I tried that. I see each bridge mapped to a interface vlan tag but this doesn't seem to leave vmbr0 untagged. In fact, If I create a new VM and I map its network card to vmbr0 I still can see, from the VM (using tcpdump), a lot of 802.1q traffic coming from other VLANs.

Thanks Alwin, as you said, if vmbr0 is not vlan_aware a separate bridge is created for every "tagged" VLAN I configure on VMs. Anyway, I would still have no way to configure a VM on a bridge created on top of the native (untagged) VLAN 1... right ?

Hello, My PVE hypervisor has an interface eth0 connected to a switch port configured as a trunk, where VLAN1 is the native (untagged) VLAN and a number of other (tagged) VLANs are allowed. On top of eth0 I created a "vlan aware" bridge, named vmbr0. When I create a network interface for a new...

It looks like disabling the GRO on the bridged NIC (eth2) has mitigated the problem. I added in /etc/network/interfaces: pre-up /sbin/ethtool -K eth2 gro off No kernel panics observed since yesterday.

Thanks Stephen, but the info in that thread don't seem to be related to my case. As a further test, today I tried to move the vmbr0 bridge on top of an Intel 82576 NIC (instead of the Intel 82574L NIC) and after a while, when all the VMs were started, I got the same kind of kernel panic (see...

Thanks Stephen, but unfortunately the kernel panics occur on the hypervisors (which have real Intel network cards). The VMs use virtio drivers and they work fine. Cheers, Rosario

Hello, I'm experiencing random kernel panics on a 6-nodes Proxmox VE cluster, recently updated to 3.4 (but they also used to occur with version 3.3). My current PVE config is: # pveversion -v proxmox-ve-2.6.32: 3.3-147 (running kernel: 2.6.32-37-pve) pve-manager: 3.4-1 (running version...