A type 1 hypervisor really is an operating system in its own right... It doesn't seem practical for Workstation to be turned into a Type 1 hypervisor that runs "on" Windows.
VMware can take responsibility for our own ability to run nested instances of VMware products and 3rd-party hypervisors, but the capacity of 3rd-party hypervisors to run nested instances of our products is really up to those 3rd party vendors. Installing the Hyper-V role on a host effectively moves "Windows" into a Hyper-V virtual machine, so any virtual machine we try to run will effectively be nested inside Hyper-V. As Microsoft continues to improve Hyper-V's nested virtualization capabilities, I'm confident that we will someday be able to run with the Hyper-V role installed on the host, but it seems we're not quite there yet.
Cheers,
--
Darius
A type 1 hypervisor really is an operating system in its own right... It doesn't seem practical for Workstation to be turned into a Type 1 hypervisor that runs "on" Windows.
VMware can take responsibility for our own ability to run nested instances of VMware products and 3rd-party hypervisors, but the capacity of 3rd-party hypervisors to run nested instances of our products is really up to those 3rd party vendors. Installing the Hyper-V role on a host effectively moves "Windows" into a Hyper-V virtual machine, so any virtual machine we try to run will effectively be nested inside Hyper-V. As Microsoft continues to improve Hyper-V's nested virtualization capabilities, I'm confident that we will someday be able to run with the Hyper-V role installed on the host, but it seems we're not quite there yet.
Cheers,
--
Darius