Shulou(Shulou.com)05/31 Report--

It is believed that many inexperienced people have no idea about the problems encountered by VMWare Workstation 14 and vsphere esxi 5.5.Therefore, this article summarizes the causes and solutions of the problems. Through this article, I hope you can solve this problem.

1. The virtual machine panicked on EXSi, but the virtual machine could not be shut down on the client. Power supply and other menus are also grayed out and cannot be used.

The newly added vm suddenly did not respond, through the remote console to see, it is also a black screen, but not all dead, send hot start keys are not reflected, power and other menus are also grayed out, can not be used.

Solution: log in to the physical server with ssh, first list the running vm with the esxcli vm process list command, and check out the World ID of the half-dead vm, such as 174184052

Then use the esxcli vm process kill-- type=force-- world-id=174184052 command to kill the process, and then turn on the power.

~ # esxcli vm process list

York-3.5

World ID: 174184052

Process ID: 0

VMX Cartel ID: 174184047

UUID: 56 4d d7 4c d8 4a fd a7-b5 40 39 67 b5 d5 94 4d

Display Name: York-3.5

Config File: / vmfs/volumes/564dba01-f43069bc-45a0-0026b93b07be/York-3.5/York-3.5.vmx

~ #

~ # esxcli vm process kill-- type=force-- world-id=174184052

2. VM vsphere esxi 5.5 nested Virtualization

Because the virtual machine I created on the server also has the virtual machine created by KVM, that is, the virtual machine is nested. I logged in to the virtual machine on EXSi, started the nested virtual machine with the command, and linux prompted that the CPU virtual related function was not turned on.

I right-click the virtual machine directly on the exsi client, Settings, options, CPU/MMU Virtualization, choose to use Interl VT-x/AMD-V instruction set virtualization, and use Interl EPT/ AMD RVI for MMU virtualization option. But when the virtual machine is turned on again, the problem still occurs.

The resolution steps are as follows:

A. Ssh login to exsi5.5

b. Modify the .vmx configuration file of the virtual machine

Go to the shell interface of exsi and find the directory corresponding to the virtual machine name under the cd / vmfs/volumes/datastore1/ directory. For example, the virtual machine name is centos.

Enter the directory

Open the centos.vmx file, append the following vhv.enable= TRUE field at the end, and save the exit.

# vi centos.vmx

Nce.enable = TRUE

Hypervisor.cpuid.v0 = FALSE

FeatMask.vm.hv.capable = "Min:1"

Vhv.enable= TRUE

There are many modifications to the overall physical server on the network, which is not feasible in my environment. The EXSI server I use also runs some formal business virtual machines, and the server cannot be restarted to make the configuration effective.

For this modification of a single virtual machine, you only need to restart the virtual machine.

After reading the above, have you mastered what are the problems encountered by VMWare Workstation 14 and vsphere esxi 5.5 respectively? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.