Michael A. Collins
2011-Dec-11 15:33 UTC
PV Drivers dropping all packets with 802.1q headers
I have serveral domUs running on xen-unstable and I''ve found that if I run Qemu emulated nics, aka HVM, the domU''s process packets whether they have a 802.1q header or not. With PV drivers that is not the case. The PV drivers on Linux or Windows, just drop all packets that contain 802.1q headers. On the Linux side I was able to get it working by creating a vlan subinterface inside the domU. I do not see how to do that with the Windows PV drivers. Is this known behavior? I have not seen anything posted here that is related. Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper
2011-Dec-11 21:36 UTC
Re: PV Drivers dropping all packets with 802.1q headers
> > I have serveral domUs running on xen-unstable and I''ve found that if Irun> Qemu emulated nics, aka HVM, the domU''s process packets whether they > have a 802.1q header or not. With PV drivers that is not the case.The PV> drivers on Linux or Windows, just drop all packets that contain 802.1q > headers. On the Linux side I was able to get it working by creating avlan> subinterface inside the domU. I do not see how to do that with theWindows> PV drivers. Is this known behavior? I have not seen anything postedhere> that is related. >Where are the packets going once they hit the DomU? Are you not using VLAN''s inside there? James
Michael A. Collins
2011-Dec-11 22:16 UTC
Re: PV Drivers dropping all packets with 802.1q headers
On 11.12.2011 16:36, James Harper wrote:>> >> I have serveral domUs running on xen-unstable and I''ve found that if >> I > run >> Qemu emulated nics, aka HVM, the domU''s process packets whether they >> have a 802.1q header or not. With PV drivers that is not the case. > The PV >> drivers on Linux or Windows, just drop all packets that contain >> 802.1q >> headers. On the Linux side I was able to get it working by creating >> a > vlan >> subinterface inside the domU. I do not see how to do that with the > Windows >> PV drivers. Is this known behavior? I have not seen anything >> posted > here >> that is related. >> > > Where are the packets going once they hit the DomU? Are you not using > VLAN''s inside there? > > James > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usersI have done that with Linux ip link settings, but I can''t find anything that would allow me to do that with the Windows GPLPV drivers. Mike
James Harper
2011-Dec-11 22:25 UTC
Re: PV Drivers dropping all packets with 802.1q headers
> > I have done that with Linux ip link settings, but I can''t findanything that> would allow me to do that with the Windows GPLPV drivers. > Mike >GPLPV doesn''t support VLAN''s, or at least I haven''t added anything that would allow them and I think Windows requires driver support. For VM''s that need access to multiple VLAN''s in Dom0 I''d normally create the multiple interfaces in Dom0 and plumb them through individually. James
Michael A. Collins
2011-Dec-12 01:03 UTC
Re: PV Drivers dropping all packets with 802.1q headers
On 11.12.2011 17:25, James Harper wrote:>> >> I have done that with Linux ip link settings, but I can''t find > anything that >> would allow me to do that with the Windows GPLPV drivers. >> Mike >> > > GPLPV doesn''t support VLAN''s, or at least I haven''t added anything > that > would allow them and I think Windows requires driver support. For > VM''s > that need access to multiple VLAN''s in Dom0 I''d normally create the > multiple interfaces in Dom0 and plumb them through individually. > > James > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usersI see. I am using Open vSwitch instead of the linux bridging, so I''ve found that it''s impossible to strip the 802.1q header before it egresses out of the switch to the domU. I am going to try their latest version that includes native-untagged mode on trunk ports. That way I can at least pass traffic for one single vlan without tags through the trunk. I think that my focus needs to be on the Open vSwitch side, since I assume it would be much easier to change the way they do access ports, then add vlan functionality to the GPLPV drivers. If there is an easier way that I might be overlooking please let me know, otherwise I''ll dig into ofproto and see what I can break. Mike