0

Recently, I had to install Docker on my Windows 10 Machine:

Edition         Windows 10 Pro
Version         21H1
Installed on    ‎08-‎08-‎2021
OS build        19043.1237
Experience      Windows Feature Experience Pack 120.2212.3530.0

For that, I had to follow this answer to get Docker up and running. After Docker was working properly I tried opening one of the VMWare VMs and I saw an error related to side-channel mitigations being enabled. I followed the solution here to fix it. After I opened the VM, it was not able to connect to the internet. I have already tried restarting the VMWare NAT and DHCP services as suggested here.

MrObjectOriented
  • 303
  • 1
  • 4
  • 8
  • Try reinstalling VMware (Workstation, I trust). Make sure you have a backup of VMware virtual machines, uninstall VMware, restart the host computer, install VMware, do a final restart and test. VMware Workstation needs to be V16.1 to coexist with Hyper-V. – John Sep 19 '21 at 11:39
  • I am using VMWare Workstation Player, and I did a fresh reinstall of VMWare Workstation Player 16.1.2 build-17966106, but it had the same issue. – MrObjectOriented Sep 19 '21 at 17:11
  • I am not sure if Player co-exists with Hyper-V. Newest version of Workstation works with Hyper-V but it is still a work in progress. – John Sep 19 '21 at 18:31

1 Answers1

0

I had this exact problem but was unable to find any information on this. However now I understand why.

In my case I had 2 guest VMs running one ubuntu 22.04 and one windows 10 both of which were in suspended state when I enabled Hyper-V features. The other day when I came to use my VMs I noticed the same side-channel related error and a prompt after that to discard VM state or keep it. The latter did not change the state of VM nor was able to run my VM so I had no choice but discarding. After that I noticed my windows VM is able to connect but my Ubuntu VM is not which is why I was suspecting the Hyper-V features. Then I tried disabling them but still no network on my Ubuntu. That was when I noticed my network adapter was disabled on Ubuntu OS and I found this solution on Internet.

To sum it up, my problem was not the Hyper-V setting but discarding the VM state (probably!). Changing Hyper-V feature settings was only the trigger to it.

e1985t
  • 1