[Bug 211062] [ixv] sr-iov virtual function driver fails to attach

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Sep 12 19:21:34 UTC 2017


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062

--- Comment #8 from Richard Gallamore <ultima at freebsd.org> ---
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 at pci0:129:0:133:    class=0x020000 card=0x00001458 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: 0000:00:06.0: enabling device (0004 -> 0006)
ixgbevf: 0000:00:06.0: PF still in reset state. Is the PF interface up?
ixgbevf: 0000:00:06.0: Assigning random MAC address
ixgbevf: 0000:00:06.0: irq 48 for MSI/MSI-X
ixgbevf: 0000: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.


More information about the freebsd-net mailing list