Date: Thu, 13 Nov 2025 13:20:09 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 290997] [vmm]: PCI passthrough on AMD Ryzen 8700G not supported yet? (Variable size IVHD type 0xf0 not supported) Message-ID: <bug-290997-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290997 Bug ID: 290997 Summary: [vmm]: PCI passthrough on AMD Ryzen 8700G not supported yet? (Variable size IVHD type 0xf0 not supported) Product: Base System Version: 15.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bhyve Assignee: virtualization@FreeBSD.org Reporter: nbe@vkf-renzel.de Hi, trying to pass through an Intel GPU card on a AMD Ryzen 8700G system. VMM loads so far, but "vm-bhyve" complains that "pci passthrough not supported on this system (no VT-d or amdvi)". And it seems to be right - looking at the dmesg: ----------------------------- SNIP ----------------------------- ppt0 mem 0xf4000000-0xf4ffffff,0xf800000000-0xfbffffffff at device 0.0 on pci3 amdviiommu0 at device 0.2 on pci0 AMD-Vi: IVRS Info VAsize = 64 PAsize = 48 GVAsize = 2 flags:0 ivhd0: <AMD-Vi/IOMMU ivhd in mixed format> on acpi0 ivhd0: Unknown dev entry:0xf0 Variable size IVHD type 0xf0 not supported ivhd0: Flag:30<IotlbSup,Coherent> ivhd0: Features(type:0x40) MsiNumPPR = 0 PNBanks= 2 PNCounters= 4 ivhd0: Extended features[31:0]:a2254afa<PPRSup,NXSup,GTSup,<b5>,IASup,GASup,PCSup> HATS = 0x2 GATS = 0x0 GLXSup = 0x1 SmiFSup = 0x1 SmiFRC = 0x1 GAMSup = 0x1 DualPortLogSup = 0x2 DualEventLogSup = 0x2 ivhd0: Extended features[62:32]:246577ef<USSup,PprOvrflwEarlySup,PPRAutoRspSup,BlKStopMrkSup,PerfOptSup,MsiCapMmioSup,GIOSup,EPHSup,InvIotlbSup> Max PASID: 0x2f DevTblSegSup = 0x3 MarcSup = 0x1 ivhd0: supported paging level:7, will use only: 4 ivhd0: device [0x3 - 0xfffe] config:0 ivhd0: device [0xff00 - 0xffff] config:0 ivhd0: PCI cap 0x190b640f@0x40 feature:19<IOTLB,EFR,CapExt> ----------------------------- SNIP ----------------------------- sysctl hw.vmm: ----------------------------- SNIP ----------------------------- #sysctl hw.vmm hw.vmm.amdvi.domain_id: 0 hw.vmm.amdvi.disable_io_fault: 0 hw.vmm.amdvi.ptp_level: 4 hw.vmm.amdvi.host_ptp: 1 hw.vmm.amdvi.enable: 0 hw.vmm.amdvi.count: 1 hw.vmm.npt.pmap_flags: 508 hw.vmm.svm.num_asids: 32768 hw.vmm.svm.disable_npf_assist: 0 hw.vmm.svm.features: 515849471 hw.vmm.svm.vmcb_clean: 1023 hw.vmm.vmx.l1d_flush_sw: 0 hw.vmm.vmx.l1d_flush: 0 hw.vmm.vmx.vpid_alloc_failed: 0 hw.vmm.vmx.posted_interrupt_vector: -1 hw.vmm.vmx.cap.posted_interrupts: 0 hw.vmm.vmx.cap.virtual_interrupt_delivery: 0 hw.vmm.vmx.cap.tpr_shadowing: 0 hw.vmm.vmx.cap.invpcid: 0 hw.vmm.vmx.cap.monitor_trap: 0 hw.vmm.vmx.cap.unrestricted_guest: 0 hw.vmm.vmx.cap.rdtscp: 0 hw.vmm.vmx.cap.rdpid: 0 hw.vmm.vmx.cap.wbinvd_exit: 0 hw.vmm.vmx.cap.pause_exit: 0 hw.vmm.vmx.cap.halt_exit: 0 hw.vmm.vmx.initialized: 0 hw.vmm.vmx.cr4_zeros_mask: 0 hw.vmm.vmx.cr4_ones_mask: 0 hw.vmm.vmx.cr0_zeros_mask: 0 hw.vmm.vmx.cr0_ones_mask: 0 hw.vmm.vmx.no_flush_rsb: 0 hw.vmm.ept.pmap_flags: 0 hw.vmm.vrtc.flag_broken_time: 1 hw.vmm.ppt.devices: 1 hw.vmm.iommu.enable: 1 hw.vmm.iommu.initialized: 0 hw.vmm.bhyve_xcpuids: 9 hw.vmm.topology.cpuid_leaf_b: 1 hw.vmm.create: hw.vmm.destroy: hw.vmm.maxcpu: 16 hw.vmm.trap_wbinvd: 0 hw.vmm.trace_guest_exceptions: 0 hw.vmm.ipinum: 252 hw.vmm.halt_detection: 1 ----------------------------- SNIP ----------------------------- Is that a known problem? Thanks and regards, Nils -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-290997-27103>