Date: Tue, 18 Jul 2023 03:24:17 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 243640] QEMU / KVM Q35 V4.X PCIe Virtual and Physical (Passthrough) Devices not detected Message-ID: <bug-243640-27103-aerWArACda@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-243640-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-243640-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243640 --- Comment #10 from John Hartley <drum@graphica.com.au> --- (In reply to John Hartley from comment #9) H Mina Galic, I have now done further testing with 13.2. You can get this up and running Q35 V4.2 & 6.2 but you need to ensure that = is is using specific OVMF (UEFI) firmwaare. My libvirt configuraton to achieve this: <WORKS> ... <os> <type arch=3D'x86_64' machine=3D'pc-q35-6.2'>hvm</type> <loader readonly=3D'yes' type=3D'pflash'>/usr/share/OVMF/OVMF_CODE.fd</= loader> <nvram>/home/XXXX/Documents/current.dev.freebsd/OVMF_VARS.fd</nvram> </os> ... </WORKS> The default UEFI / OVMF libvirt configuration is: <FAILS> ... <os firmware=3D'efi'> <type arch=3D'x86_64' machine=3D'pc-q35-6.2'>hvm</type> </os> ... </FAILS> This result in it loading a different OVMF version, which then fails UEFI b= oot. With the working boot e1000e (Intel 1GbE on PCIe bus) if found ok. So it looks like 13.2 has fixed the problem with PCIe Devices, but I have n= ot tested with real devices via PCIe passthrough... Cheers, John Hartley. --=20 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-243640-27103-aerWArACda>