[Bug 211062] [ixv] sr-iov virtual function driver fails to attach
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062 Kubilay Kocak changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2635 ||68 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 211062] [ixv] sr-iov virtual function driver fails to attach
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062 --- Comment #16 from xygzen --- Further update - to get this to work without crashing there is a patch that needs to be applied to Intel VTd in the kernel. A thread on it is here:https://forums.freebsd.org/threads/pci-passthrough-bhyve-usb-xhci.65235/ And the patch is here: https://bz-attachments.freebsd.org/attachment.cgi?id=195225 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 211062] [ixv] sr-iov virtual function driver fails to attach
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062 xygzen changed: What|Removed |Added CC||j...@iamplugged.in --- Comment #15 from xygzen --- If it helps any - I was getting the exact same issue at one cloud provider. When I enabled SR-IOV in the BIOS it had a cryptic message about needing to enable ASPM (Active State Power Management) for the SR-IOV to work properly. Nothing I did allowed it to work. When I switched providers, there was an ASPM setting in the BIOS of the new machine that wasn't there previously - and these were both Supermicro boards so it looks like not all motherboards support this functionality or maybe there is a newer version of the BIOS that has the setting correctly enabled. I still needed to enable hw.pci.honor_msi_blacklist=0 in /boot/loader.conf and used the latest IX and IXV drivers from Intel: IX - v3.3.25 - https://www.intel.com/content/www/us/en/download/14303/intel-network-adapters-driver-for-pcie-10-gigabit-network-connections-under-freebsd.html IXV -v.1.5.28 - https://www.intel.com/content/www/us/en/download/645984/intel-network-adapter-virtual-function-driver-for-pcie-10-gigabit-network-connections-under-freebsd.html Once I ran iovctl -C -f /etc/iovctl.conf the VF driver correctly attached to ixv0 (no passthrough) and the pci devices were configured correctly for the ixv1-3 for passthrough without drivers attached. Setting iovctl_files="/etc/iovctl.conf" in rc.conf and changing the ip to be configured on ixv0 instead of ix0 got this up and running automatically on reboot. If you're looking for a good cloud host with support for this I can highly recommend https://www.zare.com Hope that helps! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 211062] [ixv] sr-iov virtual function driver fails to attach
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062 tsuroer...@gmail.com changed: What|Removed |Added CC||tsuroer...@gmail.com --- Comment #12 from tsuroer...@gmail.com --- I have just run into this problem on FreeBSD 11.2 for one of my use cases. Has this problem of VFs not attaching been fixed in 11-STABLE for 11.3, 12.0-RELEASE or 12-STABLE? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 211062] [ixv] sr-iov virtual function driver fails to attach
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062 --- Comment #11 from Eric Joyner --- (In reply to Richard Gallamore from comment #10) In regards to the 63 VF limit, the card supports up to 64 (fixed) queue pools, but the current implementation always assigns one to the PF interface, so you get the 63 VF limit. If it were changed to not give the PF interface any queues, then you could have 64 VFs. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 211062] [ixv] sr-iov virtual function driver fails to attach
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062
--- Comment #10 from Richard Gallamore ---
(In reply to Piotr Pietruszewski from comment #9)
Hello Piotr,
Thank you very much for the link. After compiling and installing the driver
everything appears to work though I have noticed an errors, i'm not sure if it
is a false positive and also I think the vf is short by one. I have done basic
testing (pinging) on the vfs and seems to work fine.
Setting hw.ix.num_queues seems to no longer matter so I removed it from
/boot/loader.conf. I'm not sure if this was intentional. One error I found so
far:
Dec 21 15:50:42 S1 kernel: ix1: CRITICAL: ECC ERROR!! Please Reboot!!
Not sure if its a false positive. Seems to happen after the 3rd invoke of
iovctl after reboot, but not entirely sure of the trigger.
64 vfs per port should be available, However, vfs <= 63 everything appeared
normal other than the occasional error previously mentioned.
vfs >= 64 will return error:
iovctl: Failed to configure SR-IOV: No space left on device.
64 is supposed to be the max vfs or am I mistaken? or is the first interface
(ix1) count as one of the vfs?
FreeBSD S1 12.0-CURRENT FreeBSD 12.0-CURRENT #2 r327068: Thu Dec 21 13:00:34
PST 2017
# cat /boot/loader.conf
if_ix_load="YES"
# cat /etc/iovctl.conf
PF {
device : ix1;
num_vfs : 32;
}
DEFAULT {
passthrough : true;
}
VF-0 {
passthrough : false;
}
VF-1 {
passthrough : false;
}
It would be nice to get this in head but after seeing r327031[1], I don't see
this happening anytime soon.
Also want to mention, tested head driver(4.0.0-k) before 3.2.17 and sr-iov is
returning the similar/same errors mentioned in earlier posts on this thread.
[1] https://svnweb.freebsd.org/base?view=revision&revision=327031
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 211062] [ixv] sr-iov virtual function driver fails to attach
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062 Piotr Pietruszewski changed: What|Removed |Added CC||piotr.pietruszewski@intel.c ||om --- Comment #9 from Piotr Pietruszewski --- (In reply to Richard Gallamore from comment #8) It is likely that this bug is fixed in newest driver provided by Intel on https://downloadcenter.intel.com/download/14688/Intel-Network-Adapters-Driver-for-PCIe-10-Gigabit-Network-Connections-Under-FreeBSD- . Feedback about problem resolution would be greatly appreciated. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 211062] [ixv] sr-iov virtual function driver fails to attach
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062
--- Comment #8 from Richard Gallamore ---
Booting up a windows 10:
nice -n -20 bhyve \
-c 4 -m 8G -w -H -S \
-s 0,hostbridge \
-s 3,ahci-cd,${IMAGES}/null.iso \
-s 5,ahci-hd,${ZVOL_DIR}/${NAME} \
-s 6:0,passthru,129/0/133 \
-l bootrom,${IMAGES}/BHYVE_UEFI.fd \
-s 29,fbuf,tcp=${VNC},w=1600,h=900 \
-s 30,xhci,tablet \
-s 31,lpc -l com1,stdio \
${NAME}
pciconf -lv:
ppt0@pci0:129:0:133:class=0x02 card=0x1458 chip=0x15158086 rev=0x01
hdr=0x00
vendor = 'Intel Corporation'
device = 'X540 Ethernet Controller Virtual Function'
class = network
subclass = ethernet
While windows 10 is booting an error is received:
Assertion failed: (error == 0), function modify_bar_registration, file
/usr/src/head/src/usr.sbin/bhyve/pci_emul.c, line 491.
Abort trap
Booting a debian 8 (jessie):
nice -n -20 bhyve \
-c 2 -m 4G -w -H -S \
-s 0,hostbridge \
-s 5,ahci-hd,${ZVOL_DIR}/${NAME} \
-s 6:0,passthru,129/0/133 \
-l bootrom,${IMAGES}/BHYVE_UEFI.fd \
-s 29,fbuf,tcp=${VNC},w=1440,h=900 \
-s 30,xhci,tablet \
-s 31,lpc -l com1,stdio \
${NAME}
This boots successfully, however # dmesg | grep ixgbe has errors:
ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver -
version 2. 12.1-k
ixgbevf: Copyright (c) 2009 - 2012 Intel corporation.
ixgbevf: :00:06.0: enabling device (0004 -> 0006)
ixgbevf: :00:06.0: PF still in reset state. Is the PF interface up?
ixgbevf: :00:06.0: Assigning random MAC address
ixgbevf: :00:06.0: irq 48 for MSI/MSI-X
ixgbevf: :00:06.0: irq 49 for MSI/MSI-X
# ip link set eth0 up
ixgbevf: Unable to start - perhaps the PF Driver isn't up yet
RTNETLINK answers: Network is down
Hope this helps.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 211062] [ixv] sr-iov virtual function driver fails to attach
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062
--- Comment #7 from Richard Gallamore ---
(In reply to Eric Joyner from comment #6)
This is a FreeBSD host using the iovctl program to create vfs with the
X540-AT2 network card. I haven't attempted to test the vfs with a guest in over
a year but I doubt it will work because the error is similar or possibly same
with new error message. Also, Ultima was my old bugzilla account so sorry if
this brings some confusion.
My previous tests (over a year ago) once the iovctl command is invoked and the
vfs spawn, the network port no longer functions until iovctl removes the vfs. I
am pretty sure I have tested with and without pf on the previous test but I
can't say for certain. The recent test was with pf enabled.
When I have some time I'll do a more complete test with errors provided by the
bhyve guest as using a vf if this will help. Here are the relevant
configuration files.
loader.conf:
hw.ix.num_queues="4"
iovctl.conf:
PF {
device : ix1;
num_vfs : 4;
}
DEFAULT {
passthrough : true;
}
VF-0 {
passthrough : false;
}
VF-1 {
passthrough : false;
}
pf.conf: (omitted jail specific rules and variables to keep private)
set block-policy drop
set skip on { lo, bridge, tap } # skip on bridge and tap, they can cause issues
with bhyve
scrub all no-df max-mss 1440 random-id reassemble tcp
block on ix0 all
pass in proto tcp to $host port { $host_tcp } modulate state
pass in proto udp to $host port { $host_udp } modulate state
pass in proto tcp from $nfs_clients to $host port { $host_nfs_ports } modulate
state
pass in proto udp from $nfs_clients to $host port { $host_nfs_ports } modulate
state
pass out all modulate state
pass in inet proto icmp all icmp-type echoreq
pass in inet6 proto ipv6-icmp all icmp6-type { 1, 2, 3, 4, 128, 129, 133, 134,
135, 136, 137 }
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 211062] [ixv] sr-iov virtual function driver fails to attach
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062 Eric Joyner changed: What|Removed |Added CC||e...@freebsd.org --- Comment #6 from Eric Joyner --- (In reply to Richard Gallamore from comment #4) Err, so what's your setup again? It's hard to follow from the previous comments. Are you using a linux host with a freebsd guest? Just running the VFs alongside the PFs on the same OS? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 211062] [ixv] sr-iov virtual function driver fails to attach
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062 rahu changed: What|Removed |Added CC||rahud...@hotmail.com --- Comment #5 from rahu --- If the card you hand over is usable (either on a foundation or on the tableau), you might do so. If not, include it to a face-up dispose of stack. https://solitaire-klondike.net -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 211062] [ixv] sr-iov virtual function driver fails to attach
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062 Richard Gallamore changed: What|Removed |Added CC||ult...@freebsd.org --- Comment #4 from Richard Gallamore --- Just checking in with an update as there is a new driver version. Everything is the same except I changed num_vfs to 4 and there is a new error message. 12.0-CURRENT FreeBSD 12.0-CURRENT #3 r323109 amd64 dmsg: ixv0: at device 0.129 on pci10 ixv0: ...reset_hw() failure: Reset Failed! device_attach: ixv0 attach returned 5 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 211062] [ixv] sr-iov virtual function driver fails to attach
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062 Mark Linimon changed: What|Removed |Added Keywords||IntelNetworking Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
