Vmware with Hyper-V and / or WSL All terrible performance but can be mega improved

Hi folks
Running VM's in VMWare with WSL enabled as well as HYPER-V and Virtual Machine platform yields attrocious performance on W11 (preview).

If you want to use VMWare WKS 16.2.1 with the snappiest performance possible on a W11 Host do the following :

1) switch off HYPER-V, all the Hyper-V related things, e.g Virtual machine platform, WSL , and Windows Hyper-V platform (if you want those then either forget Vmware WKS or create another Windows installation) . Easy enough using VHDX physical devices -- you'll have to re-boot anyway changing those options so why not have a separate Windows install !!!

2) Create a VHDX physical file, mount / attach as a physical disk, attach it - and create it as a GPT drive

3) When creating the VM create the virtual hard disk as either SATA or Nvme and use "physical device" using disk created as 2) and note when editing the VM config / creating a VM on VMWare WKS with a "physical drive" you'll need to run VMWare WKS in admin mode.

4) install your VM.

Now it should positively fly as you will be using Host Disk I/O and native file systems rather than "paravirtualised Virtual Disk I/O driver" and paravirtualised file system handling.

Hope this helps people twiddling their thumbs while booting up a VM created with VMware Wks on W11 on which HYPER-V is also active.

HYPER-V alone is still probably the best but if using Linux VM's or older Windows VM's than W10 and also using "plug and play" attachment of USB devices and sensible networking VMWare WKS has improved by leaps and bounds (also with help of Ms's Physical vhdx files). For Hosts pre W10 you can't run on vhdx drives but you can still use "Physical disks". You can though run Guests on physical vhdx drives if the host is W10 or W11.

Cheers
jimbo

jimbo45 said:

Hi folks
Running VM's in VMWare with WSL enabled as well as HYPER-V and Virtual Machine platform yields attrocious performance on W11 (preview).

If you want to use VMWare WKS 16.2.1 with the snappiest performance possible on a W11 Host do the following :

1) switch off HYPER-V, all the Hyper-V related things, e.g Virtual machine platform, WSL , and Windows Hyper-V platform (if you want those then either forget Vmware WKS or create another Windows installation) . Easy enough using VHDX physical devices -- you'll have to re-boot anyway changing those options so why not have a separate Windows install !!!

2) Create a VHDX physical file, mount / attach as a physical disk, attach it - and create it as a GPT drive

3) When creating the VM create the virtual hard disk as either SATA or Nvme and use "physical device" using disk created as 2) and note when editing the VM config / creating a VM on VMWare WKS with a "physical drive" you'll need to run VMWare WKS in admin mode.

4) install your VM.

Now it should positively fly as you will be using Host Disk I/O and native file systems rather than "paravirtualised Virtual Disk I/O driver" and paravirtualised file system handling.

Hope this helps people twiiddling their thumbs while booting up a VM created with VMware Wks on W11 on which HYPER-V is also active.

HYPER-V alone is still probably the best but if using Linux VM's or older Windows VM's than W10 and also using "plug and play" attachment of USB devices and sensible networking VMWare WKS has improved by leaps and bounds (also with help of Ms's Physical vhdx files).

Cheers
jimbo

Click to expand...

You can have vmware installed as well as Hyper-V. Just create a second boot entry that boots into vmware mode without the hyypervisor running. This still works.

See option 2

cereberus said:

You can have vmware installed as well as Hyper-V. Just create a second boot entry that boots into vmware mode without the hyypervisor running. This still works.

See option 2

Run Hyper-V, VirtualBox and VMware on same Computer

How to Run Virtual Machines and any Vrtualization Software on Same Windows 10 Computer

www.tenforums.com

Click to expand...

Hi there
That also works but still the VMware performance is nothing like as good as when HYPER-V isn't enabled at all, plus using physical disks speeds stuff up no end plus you still have to re-boot so you might just as well go for separate versions of Windows -- if you separate data files you can easily get a decent windows system on around 45 - 50 GB of disk space.

Cheers
jmbo

jimbo45 said:

Hi there
That also works but still the VMware performance is nothing like as good as when HYPER-V isn't enabled at all, plus using physical disks speeds stuff up no end plus you still have to re-boot so you might just as well go for separate versions of Windows -- if you separate data files you can easily get a decent windows system on around 45 - 50 GB of disk space.

Cheers
jmbo

Click to expand...

If hypervisor is off, it should not make any difference if hyperV is installed or not.

Ivrather disagree about 2 versions of windows - twice as much maintenance.