Note: the original published in my cnblog blog: www.cnblogs.com/ElectronicM…

Operating environment:

Host OPERATING system: Windows 11 Home Chinese Edition (64-bit)

Vm version: VMware® Workstation 16 Pro 16.1.0

Vm OS: Ubuntu 20.04.3 LTS 64-bit

Vm network adapter: NAT mode

Causes of the problem:

Last night when I was using the Ubuntu virtual machine, I wanted to use the host to check some information and felt that the computer was under heavy load and the fan was too noisy, so I wanted to hang up the virtual machine and use it later. VMware displays an error message when the result is suspended:

VMware Workstation cannot be restored error: (VCPU-0), Exception 0xC0000005 (Access violation) has occurred. VMDB error -14: Pipe Connection has been broken.

By the time I open Ubuntu again, I’m not even online. When you open Ubuntu’s built-in Firefox and click the web page, firefox displays that the server cannot be connected and the Internet cannot be accessed. So, the helpless and painful correction of the road began:

Error correction process:

At first, I thought there was a problem with the DNS server because Firefox reported an error indicating that the server could not be connected. According to the method found online, I only need to change the nameserver in resolv.conf file to 8.8.8.8 [1] provided by Google, and the problem will be solved. After trying, the network is still disconnected; I changed the DNS address to 180.76.76.76 provided by Baidu. I tried again, but still could not get online, so I gave up the idea of modifying the DNS server. After that, I changed my mind and began to wonder if the problem was VMware or Windows. After a bit of bing, we found that the vCPU-0 error mentioned above was caused by a conflict between Hyper-V and Vmware. As we all know, the conflict between Win’s Hyper-V and VMware’s virtualization technology has not been a day or two. Previously in Win10 system has resolved the conflict problem, now in Win11 system again; The solution is simple: Just turn hyper-V off. As an administrator, I tried to shut hyper-V down from PowerShell [2] :

bcdedit /set hypervisorlaunchtype off
Copy the code

However, it didn’t work. After shutting down Hyper-V and restarting the VIRTUAL machine, it still couldn’t get online. So idea two is rejected. I then referred to [3] to set up the interfaces file, but it still didn’t work. At this time self-confidence fell to the bottom, almost plan to delete the virtual machine, a new use.

Solution:

Finally, what refreshed my confidence was the solution offered in [4]. In brief, the scheme is divided into three steps:

  1. Change the VM network adapter to host mode.

  2. Enter the following commands in the Ubuntu command window:

sudo service network-manager stop
sudo rm /var/lib/NetworkManager/NetworkManager.state 
sudo service network-manager start
Copy the code
  1. Switch the network adapter back to NAT/ bridge/other mode

Then open Firefox and find that the network is back to normal.

Room for improvement:

In the error correction process, I mentioned shutting down Hyper-V from PowerShell to solve the problem of virtual machine suspension. Although this method successfully corrects the VCPU-0 error, the VMDB error still exists. As a result, my virtual machine still failed to hang properly, reporting VMDB errors every time IT hung, and forcibly shutting down Ubuntu. Of course, at present, the function of virtual machine suspension is not necessary for me. This problem can be temporarily delayed and solved in the future. However, there are few tutorials on the Chinese Internet to resolve the VMDB error. So, if you know, please leave a comment and share your thoughts on how to solve this problem.

Reference links:

[1]. www.cnblogs.com/lxjshuju/p/.

[2]. Blog.csdn.net/m0_43406494…

[3]. Blog.csdn.net/CaoMei_HuaC…

[4]. www.cnblogs.com/jlf0103/p/9.