Bug 280286 - Win10 guest VM with GVT-d has Intel 630 UHD (and COM port) driver errors in FreeBSD 14.1
Summary: Win10 guest VM with GVT-d has Intel 630 UHD (and COM port) driver errors in F...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bhyve (show other bugs)
Version: 14.1-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-uboot (Nobody)
URL: https://forums.freebsd.org/threads/ex...
Keywords: bhyve, uefi
Depends on:
Blocks:
 
Reported: 2024-07-15 08:03 UTC by redmog
Modified: 2024-09-22 13:35 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (uboot)

Attachments
edk2-bhyve-g202308_5 debug log without fwcfg=qemu (103.00 KB, text/plain)
2024-07-15 08:03 UTC, redmog 		no flags Details
edk2-g202308_5 debug log with fwcfg=qemu flag (101.88 KB, text/plain)
2024-07-15 08:03 UTC, redmog 		no flags Details
edk2-bhyve-g202202_10 debug log with fwcfg=qemu flag (89.76 KB, text/plain)
2024-07-15 08:04 UTC, redmog 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description redmog 2024-07-15 08:03:07 UTC 
Created attachment 252058 [details]
edk2-bhyve-g202308_5 debug log without fwcfg=qemu

Hi,

I'm trying to pass through the 630 UHD iGPU from my i7-9700T to a Windows 10 guest.

The device shows up in Windows but encounters error code 43.

In addition, there are 4 COM ports all with error code 12.
This might be happening to other users, see comment 20 on bug 274389:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274389#c20

Reverting back to g202202_10 solves the COM port errors, but not the iGPU error.

More info on my investigation is available on the FreeBSD forum, starting here:

https://forums.freebsd.org/threads/experience-from-bhyve-freebsd-14-1-gpu-passthrough-with-windows-10-guest.94118/post-661914

Attaching debug logs from edk2-bhyve for various versions, with and without "fwcfg=qemu" flag.

I'm willing to try patches, commands, etc. or provide more info if it helps.

Thanks
Comment 1 redmog 2024-07-15 08:03:38 UTC 
Created attachment 252059 [details]
edk2-g202308_5 debug log with fwcfg=qemu flag
Comment 2 redmog 2024-07-15 08:04:09 UTC 
Created attachment 252060 [details]
edk2-bhyve-g202202_10 debug log with fwcfg=qemu flag
Comment 3 redmog 2024-07-15 08:05:22 UTC 
Typical bhyve command:

bhyve \
        -AHPSw \
        -c 4,sockets=1,cores=4,threads=1 \
        -m 16G \
        -s 0,hostbridge \
        -s 1,nvme,/zroot/bhyve/win10/disk0.img \
        -s 2,passthru,0/2/0 \
        -s 5,virtio-net,tap0,mac=58:9c:fc:00:a2:f4 \
        -s 8,fbuf,tcp=0.0.0.0:5900 \
        -s 9,xhci,tablet \
        -s 31,lpc \
        -l com1,stdio \
        -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \
        -U ede8888c-b2ee-11ed-a596-e86a64db3554 \
        win10 \
        1>edk2-debug.log 2>&1
Comment 4 redmog 2024-07-15 08:07:26 UTC 
Can't edit comments so posting correction to comment on the other bug:

bug #274389, comment #20
Comment 5 redmog 2024-07-25 09:29:32 UTC 
A quick question for bug triage / admins:

Should this bug be raised against "bhyve" component instead of sysutils/edk2 port?
Comment 6 redmog 2024-08-16 21:25:30 UTC 
Is there a checklist of prerequisites needed to get Intel iGPU passthru to work?
Or any ideas on what else I can try?