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

[bugzilla-noreply at freebsd.org]

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

--- Comment #1 from Ultima <Ultima1252 at gmail.com> ---
Just got a little more information on this. The ppt's appear to be broken as
well. I have started bhyve on a linux guest, using passthru ppt,

#!/bin/sh
IMAGES="/home/user/bhyve_images"
MAP="/home/user/bhyve_map"
#grub-bhyve \
#       -m ${MAP}/antergos.map -r hd0 \
#       -M 2G vm0
bhyveload \
        -S -m 20G -d ${IMAGES}/antergos-2016.06.18-x86_64.iso vm0
bhyve \
        -c 16 -m 20G -w -H -S \
        -s 0,hostbridge \
        -s 3,ahci-cd,${IMAGES}/antergos-2016.06.18-x86_64.iso \
        -s 5,ahci-hd,/dev/zvol/tank/bhyve/antergos \
        -s 6,passthru,129/0/133 \
        -l bootrom,${IMAGES}/BHYVE_UEFI_20160526.fd \
        -s 29,fbuf,tcp=0.0.0.0:5900,w=1440,h=900 \
        -s 30,xhci,tablet \
        -s 31,lpc -l com1,stdio \
        vm0

I'm still learning how to use bhyve, so this may not be an optimal vm startup.

bhyveload fails to start. But I use to to load the memory for bhyve to start.
Bhyve starts successfully.

Once in the vm, checked dmesg, and this is output for the vf driver trying to
attach.

ixgbevf: Intel(R) 10 Gigabite PCI express Virtual Function Network Driver -
version 2.12.1-k
ixgbevf: Copyright (c) 2009 - 2015 Intel Corporation.
ixgbevf 0000:00:06:0 enabling device (0004) -> 0006)
...snip, unrelated...
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: aa:f2:ab:a9:b1:f3
ixgbevf 0000:00:06.0: MAC: 2
ixgbevf 0000:00:06.0: Intel(R) X540 Virtual Function
IPv6: ADDRCONF(NETDEV_UP): eth0 link is not ready
...snip, unrelated...
ixgbevf: Unable to start - perhaps the PF driver isn't up yet
vboxguest: PCI device not found, probably running on physical hardware.
vboxguest: PCI device not found, probably running on physical hardware.
vboxguest: PCI device not found, probably running on physical hardware.

I'm not sure if the last 3 entries are related.

-- 
You are receiving this mail because:
You are the assignee for the bug.