Date: Tue, 27 Feb 2024 17:16:44 +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-xTpp4S52HN@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 #7 from Roger Pau Monn=C3=A9 <royger@freebsd.org> --- (In reply to Miroslav Lachman from comment #6) That's the same on Xen, the first CPUID signature is the HyperV one, but the following one is the Xen one, and we want to use the Xen one, as the Viridi= an set of features emulated by Xen is not very complete and just tested against Windows guests. This was already discussed in the differential revision of= the change for Xen: https://reviews.freebsd.org/D43508 So the question boils down to whether FreeBSD wants to treat KVM with HyperV extensions as HyperV or as KVM. I think the latter, as KVM is the real hypervisor, disguising as HyperV. --=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-xTpp4S52HN>