[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] bug in vlan offload in dom0 3.0.0 kernel?


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Thu, 29 Sep 2011 10:33:44 +1000
  • Delivery-date: Wed, 28 Sep 2011 17:35:37 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acx+PsQ9MamN0KnLTtWbPGSAI0uAUw==
  • Thread-topic: bug in vlan offload in dom0 3.0.0 kernel?

I've just upgraded some dom0's to 3.0.0 (debian kernel) and now my
vlan's aren't working properly. Traffic is transmitted and other devices
on that vlan see that traffic, and the xen machine sees the tagged
response on eth0 but the packet never makes it onto eth0.2 (vlan2). My
setup is this:

br-wan
    eth0.2 - physical network interface
    vif1.0 - virtual backend interface for vm

Here's an attempt to describe what I'm seeing for transmit:

vm eth0 - untagged packet
xen vif1.0 - untagged packet
xen br-wan - untagged packet
xen eth0.2 - untagged packet
xen eth0 - tagged packet
|
router eth0 - tagged packet
router eth0.2 - untagged packet

That all looks fine. The packets are tagged inside the vlan interface
and then tagged once they appear on the physical trunk. For receive:

router eth0.2 - untagged packet
router eth0 - tagged packet
| 
xen eth0 - tagged packet
xen eth0.2 - nothing

The nics are Intel dual port gigabit adapters - 82576. There is at least
one bug report describing similar behaviour to the above but that was
back in 2.6.x.

Has anyone else seen this problem? And more importantly, might vswitch
solve some of the above problems?

Thanks

James

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.