10,861
edits
Changes
Jump to navigation
Jump to search
<s>[https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v Many third-party Type 2 virtualization applications don't work together with Hyper-V feature from 'Control Panel/Windows Features']. Affected applications include "VMware Workstation" and "VirtualBox". These applications might not start virtual machines, or they may fall back to a slower, emulated mode ('''no''' VT-x and nested paging etc.)</s>
→Type 1 hypervisors
Hypervisors are the source of the "host" and "guest" terminology since they help clarify the specific "machine" one refers to; the host is the physical hardware and it manages the guests. Most hypervisors try and support the Open Virtualization Format (OVF) to facilitate virtual appliances which are built for a specific purpose (such as running common server software like WordPress or MediaWiki).
See [[Emulation Accuracy]] page for more information about terms like "[[Hypervisors|hypervisors]]", "[[Simulators|simulators]]", "[[Compatibility_layer|compatibility layers]]", "[[Wrappers|wrappers]]", "[[FPGA|FPGA-based hardware cloning]]" and "[[:Category:Emulators|software emulators]]".
==Type 2 hypervisors==
|[[VMware Workstation]]
|align=left|{{Icon|Windows|Linux}}
|[https://customerconnect.vmware.com/en/downloads/#all_products {{VMwareWorkstationVer}}]
|{{✗}} ||{{✓}} ||{{✓}}
|-
* ESXi (commercial hypervisor by VMware)
* Xen (open-source hypervisor developed for the Linux kernel)
* [https://serverfault.com/questions/855094/is-kvm-a-type-1-or-type-2-hypervisor KVM]
* UnRAID (commercial NAS distribution with an integrated hypervisor)
* Hyper-V (commercial hypervisor Microsoft developed for Windows. Requires a Pro, Enterprise, or Education version of Windows 8, 8.1, or 10)
* CHARM (custom type-1 hypervisor designed to run multiple complex devices, peripherals and chipsets on a single, cutting-edge Arm server, allowing to virtualize devices on their native architecture[https://support.corellium.com/charm/])
==Integrations==
If you're using Windows 10/11 for host OS you can use Hyper-V and GPU-P just like Linux GPU passthrough. [https://github.com/jamesstringerparsec/Easy-GPU-PV#prerequisites jamesstringerparsec's "Easy-GPU-PV" batch script] for making GPU Paravirtualization on Windows Hyper-V easier.
==Hyper-V Subsets==
In May 2019, Windows Subsystem for Linux 2/WSL 2 was announced, introducing important changes such as a real Linux kernel, through a subset of Hyper-V features. WSL 2 differs from [[Compatibility_layer|WSL 1]] in that WSL 2 runs inside a managed virtual machine that implements the full Linux kernel (similar to [[Android_emulators#Emulators|Windows Subsystem for Android/WSA]]). As a result, WSL 2 is compatible with more Linux binaries than WSL 1, as not all syscalls were implemented in WSL 1. There are even feature requests such as [https://github.com/microsoft/WSL/issues/7747 Gamepad support].
==Hypervisor issues==
===Hyper-V feature conflict issue===
Even though some reports consider this issue fixed via [https://www.ubackup.com/enterprise-backup/vmware-workstation-and-hyper-v-are-not-compatible.html recent updates (with VMware 15.5.6 and Windows 10 20H1)and WHP windows feature], user reports shows that it's still there. See [https://old.reddit.com/r/vmware/comments/swjp4t/running_vmware_workstation_on_a_hyperv_enabled/ this thread] for more information about this issue. Latest VirtualBox and BlueStacks versions have no problem with Hyper-V feature anymore.
==See also==
;Related to Hypervisors;* [[Windows_95/98/ME_emulators]]* [[Windows_2000/XP/Vista_emulators]]* [[MacOS]]* [[Android_emulators]];CPUs and Other chips emulation instead of virtualization;* [[POS_(Pong_Consoles)_CPUs_and_Other_Chips#x86_CPUs|x86 CPUs]]
[[Category:Computers|*]]
[[Category:Not really emulators]]
