Windows 10: VMWare / Vbox / HYPER-V Virtual Bios and Chipset

Hi folks

Does anybody here know of the specifications of the VMWare and Vbox virtual Bios and the emulation chipset they use. It must be pretty universal as the paravirtualised hardware works on most devices without issue -- i.e you can copy / move VM's more or less at will between different devices and host hardware (including CPU and GPU differences) -- assuming not using physical passthru of real HOST devices and other hardware.

On KVM/QEMU the BIOS is in the public domain so not a problem. SEABIOS for standard MBR and TIANOCORE for the EFI BIOS (also there's a secure boot option too).

I'd also be interested in the same for HYPER-V although Windows being quite strictly proprietary that might be under various "NDA's" so only give legal answers if you are in the know on that one.

Cheers
jimbo

:)

 

VMWare / Vbox / HYPER-V Virtual Bios and Chipset

Hi folks

Does anybody here know of the specifications of the VMWare and Vbox virtual Bios and the emulation chipset they use. It must be pretty universal as the paravirtualised hardware works on most devices without issue -- i.e you can copy / move VM's more or less at will between different devices and host hardware (including CPU and GPU differences) -- assuming not using physical passthru of real HOST devices and other hardware.

On KVM/QEMU the BIOS is in the public domain so not a problem. SEABIOS for standard MBR and TIANOCORE for the EFI BIOS (also there's a secure boot option too).

I'd also be interested in the same for HYPER-V although Windows being quite strictly proprietary that might be under various "NDA's" so only give legal answers if you are in the know on that one.

Cheers
jimbo

 

VMWare / Vbox / HYPER-V Virtual Bios and Chipset

I'll only add some brief info on what I know.

VirtualBox emulates ICH9 or PIIX3 chipset.
I didn't find much documentation about those but there is some in the manual to begin with and gets elaborated on the Vbox forum at some topics. The choice of chipset depends on selected guest since it must be supported by OS.
Chapter 3. Configuring Virtual Machines (chapter 3.5.1)
BIOS / EFI implementation must be open source but I'm no expert and I didn't dug in the sources to check. Though you can.
All settings can be changed in the VM file with .vbox extension which uses XML and so it's pretty much the closest 'structural' match to KVM / libvirt where XML is also used.

VMWare uses Phoenix BIOS, pretty much tailor-made for the hypervisor. I don't know much on this one so I'll see if someone else has more facts / data on this.

Hyper-V hides most of the boot stuff and VMs are stored in an own special format. I'm also curious about this one.

 

HYPER-V and VMWare / VBOX concurrently

The reason VBox works with Hyper-V role enabled is because they changed their program to make use of the Windows Hypervisor Platform API released in 1809. When VT-x is unavailable VBox will try to fallback to use the Hyper-V framework (a.k.a. NEM or Native Execution Manager). See VirtualBox 6.0 and Hyper-V

Android Emulator has also been updated to use this but apparently VMWare hasn't yet although according to this blog they are developing it.

Comparing Hyper-V with KVM is difficult as they work differently. Whether it is a type 1 or type 2 (or even if such a distinction makes sense any more) is debatable. See Is KVM a type 1 or type 2 hypervisor?