https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277326
--- Comment #9 from Roger Pau Monné ---
(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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277326
er...@microsoft.com changed:
What|Removed |Added
CC||er...@microsoft.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277326
--- Comment #7 from Roger Pau Monné ---
(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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277326
Miroslav Lachman <000.f...@quip.cz> changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277326
--- Comment #5 from Zhenlei Huang ---
(In reply to Zhenlei Huang from comment #4)
> 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
>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277326
--- Comment #4 from Zhenlei Huang ---
(In reply to Roger Pau Monné 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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277326
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualization@FreeBSD.org
--
You
