![]() ![]() It is because once we enable the Hyper-V, the Intel VT-X instruction that let it uses to create virtualization environment is no longer accessible from your type-2 virtual machine, only the host which in this case is Microsoft Hypervisor has the right, thus in result, platforms like VirtualBox, VMware Player & workstation couldn’t access the host VT capabilities as Windows 10 itself runs as a VM. Nevertheless, being a Virtualization veteran company, it also offers VMware ESXi as a Type-1 alternative to Hyper-V.īut the question remains the same, why we couldn’t use Type-1 and Type-2 VM platform together. ![]() However, in VMware workstation case, it installed on Windows 10 host as a software application and uses the host OS to communicate and access the hardware. ![]() To know more about it see Wikipedia page on it. The VMBus is a logical channel which enables inter-partition communication. In this way, whatever, VM we are running on this type -1 hypervisors access the hardware via VMBus partition. ![]() Now, what is the reason, why we couldn’t run earlier them together? It is because the HyperV is a Type- 1 hypervisor while VMware Workstation is Type 2 which runs on the OS, here Windows 10, whereas Hyper-V itself an OS, thus it converts and uses whole Windows 10 host as a Virtual Machine. But now it is, now we can run WSL2 (Windows subsystem for Linux) or Hyper-V along with VMWare workstation Pro 20H1. However, it was not possible earlier these two to run at once on a single machine, we have to turn off Hyper-v, first to get the Workstation of Vmware working. It has been a very long time people are looking for a way to run Vmware Workstation and Hyper-V together on the same Windows 10 machine. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |