Hi, The Intel NIC works correctly in the native FreeBSD. I used it there before I did the passthrough. The Intel NIC worked correctly natively when I tested the OpenBSD installer. The Intel NIC works in bhyve if I install FreeBSD.
The new Broadcom NIC also works normally as long as it's not a OpenBSD instance in bhyve. The NICs are not assigned to other hosts. The settings for virtualization on the hardware are correct to my knowledge. I have several other hosts running in bhyve without problems. One FreeBSD host using passthrough the same way as I intend to do with OpenBSD. On Thu, Jul 5, 2018 at 4:55 PM Tom Smyth <tom.sm...@wirelessconnect.eu> wrote: > Hello Farid, > > > Can you confirm that other operating systems pick up the Nic ok and > they function ok > > has the Physical Host settings been setup correctly for SR-IOV > > is it possible that the nic has been assigned to another vm ? > > Hope this helps > > > On 5 July 2018 at 15:38, Farid Joubbi <djfa...@gmail.com> wrote: > > I realize now that I wrote a reply to only Mike and not the whole misc > > earlier. > > > > Anyway. > > The server is running several functions, and it's not popular to do > > maintenance on it. > > I went ahead and rebooted it anyway since this is important ;-) > > > > I booted the OpenBSD 6.3 install media natively on the hardware. > > It found all six NICs that I have installed. There are two Broadcom on > the > > mainboard and four on the Intel card. > > Broadcoms were found as bge and Intel as em. They all seemed to work. > > > > I had an extra bge card lying around. I installed it in the server and > did > > PCI passthrough with it as well as the Intel in FreeBSD/bhyve. > > I get the same result in OpenBSD: > > bge0 at pci0 dev 5 function 0 "Broadcom BCM5720" rev 0x00, BCM5720 A0 > > (0x5720000), APE firmware NCSI 1.4.12.0: couldn't map interrupt > > > > Conclusion: > > The problem has to do with the fact that bhyve is between the hardware > and > > OpenBSD. > > > > Any ideas? > > > > On Thu, Jul 5, 2018 at 2:31 AM Mike Larkin <mlar...@azathoth.net> wrote: > > > >> On Thu, Jul 05, 2018 at 03:36:17AM +0200, Farid Joubbi wrote: > >> > Hi, > >> > > >> > I have a server running bhyve in FreeBSD. I did PCI passthrough in > order > >> > to have exclusive access to one of the network interfaces on the > server. > >> > My plan was to use that NIC in OpenBSD. Unfortunately when I boot the > 6.3 > >> > release installer I get this in dmesg: > >> > "em0 at pci0 dev 5 function 0 "Intel 82576" rev 0x01: couldn't map > >> > interrupt". > >> > > >> > The installation goes through without errors, but the Intel NIC is not > >> > visible during install or after rebooting the installed system. > >> > > >> > Man pages suggest that the problem is a fatal initialization error. > >> > > >> > The NIC works without problems installing FreeBSD. > >> > In FreeBSD the NIC uses the igb driver. > >> > > >> > https://man.openbsd.org/FreeBSD-11.1/igb.4 > >> > > >> > The OpenBSD man page for em lists 82576EB as supported. > >> > > >> > The NIC is an Intel Gigabi ET2 quad: > >> > > >> > https://ark.intel.com/products/series/46841/Intel-Gigabit-ET-Server-Adapter-Series > >> > > >> > Could it be that the quad variant of the NIC is not supported by > OpenBSD? > >> > Is there anything I can do to make it work? > >> > Is it possible to use the igb driver in OpenBSD somehow? > >> > > >> > Thanks. > >> > >> Before anyone at all spends any time on this, please verify if this > works > >> without bhyve in the way. Eg, boot natively on this hardware and see. > >> > >> Or did you already do that? In which case the commentary about bhyve is > >> extraneous. > >> > >> -ml > >> > > > > -- > Kindest regards, > Tom Smyth > > Mobile: +353 87 6193172 > The information contained in this E-mail is intended only for the > confidential use of the named recipient. If the reader of this message > is not the intended recipient or the person responsible for > delivering it to the recipient, you are hereby notified that you have > received this communication in error and that any review, > dissemination or copying of this communication is strictly prohibited. > If you have received this in error, please notify the sender > immediately by telephone at the number above and erase the message > You are requested to carry out your own virus check before > opening any attachment. >
