I'll try virtualbox again, but it booted fine when I tried it before.
I'll give bhyve a sping. I haven't tried it in quite some time, but
it worked about 9 months ago.
But since I don't even know what the errors you are seeing are,
I can't tell you that it is similar to some other error reports or
The sr-iov vf driver is failing to attach.
# pciconf -lv: (filtered to only relevant output)
ix0@pci0:129:0:0: class=0x02 card=0x1458 chip=0x15288086 rev=0x01
hdr=0x00
vendor = 'Intel Corporation'
device = 'Ethernet Controller 10-Gigabit X540-AT2'
class = network
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
It sounds like the bug I reported a while ago, but on a different chip
family:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207602
On Sunday, April 24, 2016, Vesselin Mirewski wrote:
> Hi,
> I'm trying to bring up an excellent PCIe Fusion board which has no driver
> for FreeBSD. I used bhy
Hi,
I'm trying to bring up an excellent PCIe Fusion board which has no driver
for FreeBSD. I used bhyve to bring up an ubuntu server ( which has an
original driver by the manufacturer )
All went just fine, till I tried to pass through the board to the linux.
My CPUs support all that's needed by bhy
On Fri, 15 Apr 2016 11:44:43 +0300
Ivan Klymenko wrote:
> On Thu, 14 Apr 2016 16:42:33 -0600
> Warner Losh wrote:
>
> > The CAM I/O scheduler has been committed to current. This work is
> > described in
> > https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf though the
> > default schedul
kristof added inline comments.
INLINE COMMENTS
sys/netpfil/pf/pf_if.c:130 I don't understand why this is required. Surely if
an ifnet lives in V_ifnet (so, lives in the current vnet) ifp->if_vnet is
always going to be curvnet?
sys/netpfil/pf/pf_if.c:141 Why add curvnet here?
pfi_attach_ifn
