Stopped working OS-configured VLAN tagged network inside Linux guests

[melanch0lia]

Remark: VLAN is configured INSIDE linux guests, not in host Debian.

Hello,

Linux host 2.6.32-41-pve #1 SMP Sat Sep 12 13:10:00 CEST 2015 x86_64 GNU/Linux

pve-manager/3.4-11/6502936f (running kernel: 2.6.32-41-pve)

After latest apt-get upgrade stopped working VLAN tagged network inside KVM Linux guests (CentOS 6.6)

dpkg.log: http://pastebin.com/dgCnJDZ5

Guest can't ping machine in same VLAN, while the PHYSICAL machine using absolutely same connection in the same network switch can ping others in same VLAN.

4: eth0.10@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether da:2e:2c:0f:42:b9 brd ff:ff:ff:ff:ff:ff
inet 172.16.11.89/24 brd 172.16.11.255 scope global eth0.10
inet6 fe80::d82e:2cff:fe0f:42b9/64 scope link
valid_lft forever preferred_lft forever

# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.16.11.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0.10

When I run tcpdump I see only ARP request and reply frames with the proper VLAN header and correct tag value.

Driver used: e1000 (tried to switch to rtl8139/virtio - no effect)

Nothing was changed else, only apt-get dist-upgrade applied.

If I create additional interface in Proxmox not configuring in OS, specifying VLAN ID, it WORKS.

What may be the problem?

 

[melanch0lia]

Reverting to 2.6.32-39-pve from 2.6.32-41-pve fixes the problem.
Couldn't even think that this is related.

Repeatedly reproduced on two separate Proxmox VEs.


The only changes I see:

pve-kernel-2.6.32 (2.6.32-164) unstable; urgency=low


  * update to latest stable vzkernel-2.6.32-042stab111.12.src.rpm


 -- Proxmox Support Team <support@proxmox.com>  Sun, 04 Oct 2015 11:28:24 +0200


pve-kernel-2.6.32 (2.6.32-163) unstable; urgency=low


  * openvswitch: fix ovs_netdev_get_vport


 -- Proxmox Support Team <support@proxmox.com>  Tue, 15 Sep 2015 13:55:41 +0200


pve-kernel-2.6.32 (2.6.32-162) unstable; urgency=low


  *  openvswitch: do not export br_should_route_hook


 -- Proxmox Support Team <support@proxmox.com>  Mon, 14 Sep 2015 11:04:21 +0200


pve-kernel-2.6.32 (2.6.32-161) unstable; urgency=low


  * update to latest stable vzkernel-2.6.32-042stab111.11.src.rpm


 -- Proxmox Support Team <support@proxmox.com>  Sat, 12 Sep 2015 12:47:14 +0200


pve-kernel-2.6.32 (2.6.32-160) unstable; urgency=low


  * use zfs/spl sources from our zfs userspace tool (to avoid 
  version mismatch)


 -- Proxmox Support Team <support@proxmox.com>  Fri, 31 Jul 2015 06:16:48 +0200


pve-kernel-2.6.32 (2.6.32-159) unstable; urgency=low


  * update to latest stable vzkernel-2.6.32-042stab108.8.src.rpm


 -- Proxmox Support Team <support@proxmox.com>  Fri, 24 Jul 2015 10:55:18 +0200

PS. There's http://forum.proxmox.com/threads/23...ing-anymore-after-newest-Update-of-pve-kernel - is it related? I don't use openVSwitch.