https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277326
--- Comment #9 from Roger Pau Monné <roy...@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-native HyperV, then the HyperV code should be adjusted to deal with it. It's however 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 assistances or devices couldn't result in failure. -- You are receiving this mail because: You are the assignee for the bug.
