User Profile
ziomario
Copper Contributor
Joined 5 years ago
User Widgets
Recent Discussions
Passthru my RTX 2080 ti from FreeBSD to a Windows 11 vm (it generates a resource conflict)
Hello to everyone. What I would like to understand if why,when I try to passthru my RTX 2080 ti from FreeBSD to Windows 11,it won't do it,causing the error 12. It says that it generates a resource conflict and requires additional installation). I'm trying to debug the error. Below you see the IOMMU group of my Nvidia Geforce RTX 2080 ti passed in a Windows 11 / bhyve VM and of Windows 11 installed physically. I'm not able to understand if there are inconsistencies. VM : Group: 30.0.15.1123 - Device: NVIDIA GeForce RTX 2080 Ti (Device ID: PCI\VEN_10DE&DEV_1E04&SUBSYS_250319DA&REV_A1\3&61AAA01&0&48) Group: 4.39.0.0 - Device: NVIDIA Virtual Audio Device (Wave Extensible) (WDM) (Device ID: ROOT\UNNAMED_DEVICE\0000) Group: 1.46.831.832 - Device: NVIDIA USB Type-C Port Policy Controller (Device ID: PCI\VEN_10DE&DEV_1AD7&SUBSYS_250319DA&REV_A1\3&61AAA01&0&4B) Group: 10.0.22000.2360 - Device: Controller host NVIDIA USB 3.10 eXtensible - 1.10 (Microsoft) (Device ID: PCI\VEN_10DE&DEV_1AD6&SUBSYS_250319DA&REV_A1\3&61AAA01&0&4A) Physical installation : Group: 31.0.15.5222 - Device: NVIDIA GeForce RTX 2080 Ti (Device ID: PCI\VEN_10DE&DEV_1E04&SUBSYS_250319DA&REV_A1\4&94764DC&0&0009) Group: 4.49.0.0 - Device: NVIDIA Virtual Audio Device (Wave Extensible) (WDM) (Device ID: ROOT\UNNAMED_DEVICE\0000) Group: 1.50.831.832 - Device: NVIDIA USB Type-C Port Policy Controller (Device ID: PCI\VEN_10DE&DEV_1AD7&SUBSYS_250319DA&REV_A1\4&94764DC&0&0309) Group: 10.0.22000.2360 - Device: NVIDIA USB 3.10 eXtensible Host Controller - 1.10 (Microsoft) (Device ID: PCI\VEN_10DE&DEV_1AD6&SUBSYS_250319DA&REV_A1\4&94764DC&0&0209) As an experiment I've passed only this device from FreeBSD to WIndows 11 : pptdevs="2/0/0" I have excluded "2/0/1 ; 2/0/2 ; 2/0/3". I want to show you what means these addresses : 02:00.0 VGA compatible controller: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti] (rev a1) 02:00.1 Audio device: NVIDIA Corporation TU102 High Definition Audio Controller (rev a1) 02:00.2 USB controller: NVIDIA Corporation TU102 USB 3.1 Host Controller (rev a1) 02:00.3 Serial bus controller: NVIDIA Corporation TU102 USB Type-C UCSI Controller (rev a1) What happened when I launched the vm using these parameters ? bhyve -S -c sockets=2,cores=2,threads=2 -m 4G -w -H -A \ -s 0,hostbridge \ -s 1,ahci-hd,/mnt/$vmdisk0'p2'/bhyve/img/Windows/Windows11.img,bootindex=1 \ -s 9:0,passthru,2/0/0 \ -s 11,hda,play=/dev/dsp,rec=/dev/dsp \ -s 13,virtio-net,tap18 \ -s 29,fbuf,tcp=0.0.0.0:5918,w=1600,h=950,wait \ -s 30,xhci,tablet \ -s 31,lpc \ -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI_CODE.fd \ vm0:18 < /dev/null & sleep 2 && vncviewer 0:18 this error : Assertion failed: (!err), function hda_init, file /usr/corvin-src-releng-140/usr.sbin/bhyve/pci_hda.c, line 353. The error is caused by this parameter : -s 11,hda,play=/dev/dsp,rec=/dev/dsp \ I have excluded it and Windows 11 booted. Now,inside it I still see the error 12 : The device PCI\VEN_10DE&DEV_1E04&SUBSYS_250319DA&REV_A1\3&61aaa01&0&48 generates a resource conflict and requires additional installation. If I pass to the vm only -s 9:0,passthru,2/0/0 \ ; it does not work anyway,because AFAIK,MAYBE there is one and only IOMMU group,so I should pass everything ? But if I pass everything,the error 12 is there anyway. I would like to understand if there is a problem with the IOMMU thing,if there is maybe there is the needing to develop a patch like this one : GitHub - benbaker76/linux-acs-override for FreeBSD. For an experienced developer should not be so hard to understand which devices conflict. I want to ask some help to understand how to debug the error. If we will be able to understand which devices conflict,maybe I can explain this to the bhyve developer with which I'm in contact and he can develop a patch. So,we will be able to use every modern nvidia gpus inside a Windows VM with bhyve under FreeBSD ! That's a nice goal,isn't it ? So,please ask me more informations that you need to understand the origin of the error. Windows Build/Version10.0.22000.2538Windows 11 Build 22.000.co_release.210604-1628 won't upgrade to 22543.1000 (rs_prerelease).
Hello. From a long time I tried to upgrade my Windows 11 Build 22.000.co_release.210604-1628 to Windows 11 Insider Preview 22543.1000 (rs_prerelease),but everytime I get the error "Installation error - 0x800700c1" and it won't complete. I'm not so experienced. Do you want to explain how can I fix this error ? thanks.ACS and ASPM are enabled,but the DDA survey script failed everywhere.
Hello. I'm trying to prepare my system to run succesfully the SurveyDDA.ps1 script because I want to pass some device from Windows server host os to the guest OS. My motherboard is Gigabyte Aorus pro. Some time ago I've asked to Gigabyte how to enable the ACS and they sent to me the lastest BIOS upgrade. So,I went on the BIOS to check if the ACS was enabled but it was already enabled. So,good,I've installed Windows server 2019 standard edition and I've installed and enabled hyper-V. After that,I went on this website : https://github.com/MicrosoftDocs/Virtualization-Documentation/blob/live/hyperv-tools/DiscreteDeviceAssignment/SurveyDDA.ps1 and I've got the script. So. Test done with : ACS enabled ; Windows server 2019 standard edition ; Hyper-V installed and enabled ; BIOS version : Z390AORUSPROGA9.F12g Product Name: Z390 AORUS PRO (1.0) BIOS Ver: Z390AORUSPROGA9.F12g Purchase Dealer: Amazon Brand: Nvidia Model: RTX 2080 ti Model: I9-9900k Operating System: other - Windows server 2019 SP: 17763.rs5_release.180914-1434 HyperX-Predator Size: 32 GB Power Supply: 600 Memory Part No.: DDR4-HX430C15PB3K2-32 PS C:\users\administrator\Desktop> .\survey-dda.ps1 Generating a list of PCI Express endpoint devices Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft)BIOS requires that this device remain attached to BIOS-owned memory. Not assignable. High Definition Audio ControllerOld-style PCI device, switch port, etc. Not assignable. NVIDIA USB Type-C Port Policy ControllerBIOS kept control of PCI Express for this device. Not assignable. Intel(R) Host Bridge/DRAM Registers - 3E30BIOS requires that this device remain attached to BIOS-owned memory. Not assignable. NVIDIA GeForce RTX 2080 TiBIOS kept control of PCI Express for this device. Not assignable. Intel(R) 300 Series Chipset Family SATA AHCI ControllerOld-style PCI device, switch port, etc. Not assignable. NVIDIA USB 3.10 eXtensible Host Controller - 1.10 (Microsoft)BIOS kept control of PCI Express for this device. Not assignable. Intel(R) Management Engine InterfaceOld-style PCI device, switch port, etc. Not assignable. Intel(R) SMBus - A323Old-style PCI device, switch port, etc. Not assignable. Intel(R) Thermal Subsystem - A379Old-style PCI device, switch port, etc. Not assignable. High Definition Audio ControllerBIOS kept control of PCI Express for this device. Not assignable. Intel(R) PCI Express Root Port #9 - A330Old-style PCI device, switch port, etc. Not assignable. Intel(R) PCI Express Root Port #1 - A338Old-style PCI device, switch port, etc. Not assignable. PCI standard RAM ControllerOld-style PCI device, switch port, etc. Not assignable. Intel(R) SPI (flash) Controller - A324Old-style PCI device, switch port, etc. Not assignable. Intel(R) PCIe Controller (x16) - 1901Old-style PCI device, switch port, etc. Not assignable. Intel(R) UHD Graphics 630BIOS requires that this device remain attached to BIOS-owned memory. Not assignable. Intel(R) Ethernet Connection (7) I219-VOld-style PCI device, switch port, etc. Not assignable. Intel(R) 300 Series Chipset Family LPC Controller (Z390) - A305Old-style PCI device, switch port, etc. Not assignable. Intel(R) PCI Express Root Port #17 - A340Old-style PCI device, switch port, etc. Not assignable. Unfortunately, this machine doesn't support using them in a VM. To use SR-IOV on this system, the system BIOS must be updated to allow Windows to control PCI Express. Contact your system manufacturer for an update.SR-IOV cannot be used on this system as the PCI Express hardware does not support Access Control Services (ACS) at any root port. Contact your system vendor for further information. Infact when I tried to dismount the graphic card from Windows Server 2019,this is what happened : PS C:\Users\Administrator\Downloads\cmder> $vmName = 'VM' PS C:\Users\Administrator\Downloads\cmder> $instanceId = 'VEN_10DE&DEV_1E04' PS C:\Users\Administrator\Downloads\cmder> $vm = Get-VM -Name $vmName PS C:\Users\Administrator\Downloads\cmder> $dev = (Get-PnpDevice -PresentOnly).Where{ $_.InstanceId -like $instanceId } PS C:\Users\Administrator\Downloads\cmder> Disable-PnpDevice -InstanceId $dev.InstanceId -Confirm:$false OK. PS C:\Users\Administrator\Downloads\cmder> Dismount-VMHostAssignableDevice -LocationPath "PCIROOT(0)#PCI(0100)#PCI(0000)" Dismount-VMHostAssignableDevice : The operation failed.The current configuration does not allow for OS control of the PCI Express bus. Please check your BIOS or UEFI settings. But,as u can see below,the ACS is enabled : as well as the ASPM : what's wrong ? what's missing ? Should I enable SR-IOV ? I don't have this option on the BIOS. Am I forgetting something ?
