Date: Tue, 27 Feb 2024 15:21:05 +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-KSjVyKOwC2@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 #4 from Zhenlei Huang <zlei@FreeBSD.org> --- (In reply to Roger Pau Monn=C3=A9 from comment #3) > Hm, I guess I'm a bit confused. While debugging PR 274810, I see the behavior, that FreeBSD guests report HyperV rather than KVM when Hyper-V enlightenment is enabled. > If the hypervisor is KVM, shouldn't it be detected as KVM rather than Hyp= erV? I think KVM should be reported. But it seems everything goes right even Hyp= erV is reported. > What's the benefit of using the HyperV enlightenments when running on QEM= U/KVM? I think Microsoft people are more familiar with that. When debugging PR 274= 810 I read briefly the design of Hyper-V virtual devices. I think the design is pretty clear and performant. I see lots of comparing of vm_guest in hyperv device drivers. I guess they should be removed to correctly probe Hyper-V devices, to correctly support Hyper-V enlightenment feature. --=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-KSjVyKOwC2>