Date: Wed, 08 May 2024 07:32:06 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 277326] FreeBSD guest on QEMU with Hyper-V enlightenment on is no longer able to detect Hyper-V devices Message-ID: <bug-277326-27103-52kfskwv09@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-277326-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-277326-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=3D277326 --- Comment #9 from Roger Pau Monn=C3=A9 <royger@freebsd.org> --- (In reply to ernis from comment #8) I'm not doing any work on this because I think there's nothing to be fixed. If FreeBSD runs on QEMU, and QEMU exposes part of the Viridian extensions, = the primary hypervisor should still be reported as QEMU, and hence the CPUID detection is accurate. The fact it was not like this originally is in my opinion a bug, and not a behavior we should carry moving forward. If there's a desire to use Viridian based extensions or devices on non-nati= ve HyperV, then the HyperV code should be adjusted to deal with it. It's howe= ver complicated, as it's my understanding most hypervisors that expose part of = the Viridian extensions do so with Windows guests in mind only. It's unclear whether enabling both HyperV and native hypervisor virtualization assistanc= es or devices couldn't result in failure. --=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-277326-27103-52kfskwv09>