Date: Wed, 09 Sep 2015 06:06:20 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 202983] ixv driver in 11.0-CURRENT(10.1 & 10.2 RELEASE) doesn't pass traffic using XEN hypervisor(AWS EC2) Message-ID: <bug-202983-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202983 Bug ID: 202983 Summary: ixv driver in 11.0-CURRENT(10.1 & 10.2 RELEASE) doesn't pass traffic using XEN hypervisor(AWS EC2) Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: jlpetz@gmail.com Created attachment 160852 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160852&action=edit 10.2 dmesg Similar problem to Bug 202875 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202875 Only the Hypervisor host is Xen+Qemu/EC2 I have ready access to AWS for testing of a guest ixv(Xen DomU) http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html. The driver detects the hardware correctly and sets everything up. But DHCP fails as there is no received packets(created guest packet capture in rc.d) from the the host Dom0. Unfortunately I can't check the host system with a packet capture as this is a IaaS platform. But on the upside you can be pretty much be guaranteed the host is setup fine for the guest as Linux/Windows work fine. I have spoken with both Colin Percival, Jack Vogel(Intel), George Neville-Neil and Jeffrey Pieper about this previously but never filed a bug for it. https://lists.freebsd.org/pipermail/freebsd-xen/2014-May/002114.html The last I heard on this was that it wass suspected to be a Xen+Qemu issue since KVM was working. However it seems more likely to be a that different host drivers as incompatible with certain guest drivers(based on below) and the fact KVM also has a bug report now(Bug 202875)? ------------------------------ > Since KVM works and Xen does not, this is basically a qemu issue. I'll > cut and paste my original findings: > > All, > > I was able to reproduce the failure Colin was seeing on SRIOV with Xen > and FreeBSD 9.2/ixgbe-2.5.15. I used SLES11-SP3 w/ Xen. I could not > acquire a dhcp license and nor could I pass traffic through the VF with > a manually assigned IP address. I tested this with the driver both > compiled in and out of the kernel. The interesting point is that the > exact same configuration works on RHEL 6.5 KVM. > > The good news, however is that FreeBSD 10.0/ixgbe-2.5.18 DOES work, with > the driver compiled both in and out of the kernel. I am able to acquire > a dhcp license at boot as well as pass traffic with a manually assigned > IP address. Another interesting data point is that with both > 9.2/ixgbe-2.5.18 and 10.0/2.5.18 both running in VMs and each assigned a > VF belonging to the same PF, 10.0/ixgbe-2.5.18 did not work either. > > I also attempted to use our out-of-tree ixgbe-2.5.18 on 9.2, but I get > SIOCGIF: ix0 no such device errors when attempting to acquire a dhcp > address or even assign an address manually. > > > Jeff ------------------------------ -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202983-8>