[Bug 260148] passthru stopped working

From: <bugzilla-noreply_at_freebsd.org>
Date: Tue, 30 Nov 2021 22:40:43 UTC

            Bug ID: 260148
           Summary: passthru stopped working
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Keywords: bhyve
          Severity: Affects Only Me
          Priority: ---
         Component: bhyve
          Assignee: virtualization@FreeBSD.org
          Reporter: bz@FreeBSD.org

I've updated my system to n251155-57512573ae05 and suddenly I am getting:

bhyve: Failed to map MSI-X table BAR on 2/0/0: Device busy
bhyve: failed to initialize BARs for PCI 2/0/0
device emulation initialization error: Device busy

when restarting my development VM.

I hadn't seen this problem in the last months while working on iwlwifi (since
it was made work).

ppt0@pci0:2:0:0:        class=0x028000 rev=0x1a hdr=0x00 vendor=0x8086
device=0x2723 subvendor=0x1a56 subdevice=0x1653
    vendor     = 'Intel Corporation'
    device     = 'Wi-Fi 6 AX200'
    class      = network
    bar   [10] = type Memory, range 64, base 0x9e200000, size 16384, disabled
    cap 01[c8] = powerspec 3  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit 
    cap 10[40] = PCI-Express 2 endpoint max data 128(128) FLR RO NS
                 max read 128
                 link x1(x1) speed 5.0(5.0) ASPM L1(L1) ClockPM enabled
    cap 11[80] = MSI-X supports 16 messages
                 Table in map 0x10[0x2000], PBA in map 0x10[0x3000]
    ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected
    ecap 0018[14c] = LTR 1
    ecap 001e[154] = L1 PM Substates 1
     Corrected = Advisory Non-Fatal Error

The driver for the guest device hasn't updated in 2-ish weeks either so it's
not due to updating the guest.

It might be a result of a weird state situation of the driver in the guest
(firmware paniced) but that shouldn't leave us with something we cannot get
back up on next guest start.  There've been recent changes to bhyve in that
area so it may as well be a side-effect of those?

I figured I am documenting this before rebooting my host now.

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