Forced handling of VM virtual machine not restarting shutdown

There is a virtual machine can not be connected to the normal network, through the vsphere client connected to the VC, it can not be restarted and shutdown operation, specific error

650) this.width=650; "src=" http://s5.51cto.com/wyfs02/M01/79/9C/wKiom1aWEX3w8ZGuAAGu41PLTb4935.jpg "title=" 89.jpg "alt=" Wkiom1awex3w8zguaagu41pltb4935.jpg "/>

Viewing event logs

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/79/9B/wKioL1aWEgnxBIg1AAIz9J-q5W4974.jpg "title=" 891. JPG "alt=" wkiol1awegnxbig1aaiz9j-q5w4974.jpg "/>

The original is the implementation of the Vmtools installation program problems, asked the implementation engineer, the original is to carry out the Vmtools upgrade did not succeed in the problem, the virtual machine now hangs dead without any response.

There is no response to the restart and shutdown, this virtual machine hangs a lot of RDM bare disk, is a storage monitoring machine. The problem needs to be resolved immediately, and the removal is obviously too late.

Then is there any other way to force the virtual machine or restart it?

A method is described below.

First turn on the SSH connection function of the ESXi host where the virtual machine resides.

650) this.width=650; "src=" http://s5.51cto.com/wyfs02/M00/79/9B/wKioL1aWE4SwjyAJAAOJpVZfrq4047.jpg "title=" 893. JPG "alt=" wkiol1awe4swjyajaaojpvzfrq4047.jpg "/>

Then connect to the command line

Perform a process view to see the process for each virtual machine

# esxcli VM Process List|more

F9emcse01

World id:40008824

Process id:0

VMX Cartel id:40008821

uuid:42 0a D0 B7 7d-61 5e 4c ab d5 5b F0 6c

Display name:f9emcse01

Config File:/VMFS/VOLUMES/55813F75-C661C1AC-DEA8-6C0B8462A7E8/F9EMCSE01/F9EMCSE01.VMX

# esxcli VM process Kill--type=

Error:missing Required Parameter-w|--world-id

USAGE:ESXCLI vm process Kill [cmd options]

Description:

Kill used to forcibly kill Virtual machines that is stuck

and not responding to normal stop operations.

CMD options:

-t|--type=<str> the type of kill operation to attempt. There is three

Types of VMS kills that can be attempted: [Soft,

Hard, force]. Users should always attempt ' soft ' kills

First, which'll give the VMX process a chance to

Shutdown cleanly (like kill or kill-sigterm). If that

Does not work move to ' hard ' kills which would shutdown

The process immediately (like kill-9 or kill

-sigkill). ' Force ' should is used as a last resort

Attempt to kill the VM. If all three fail then a

Reboot is required. (required)

-w|--world-id=<long> the World ID of the "Virtual Machine" to kill. This can

be obtained from the ' VM Process List ' command

(required)

There are three types of soft that kill the virtual machine process. Hard is forced to kill, similar to KILL-9. Force is to kill the entire virtual machine.

EXECUTE statement

# esxcli VM process kill--type=hard--world-id=40008824

found that the virtual machine has been forced to shut down, and then restart the normal, upgrade vmtools success.

This article is from the "Hollows Jie Sun" blog, be sure to keep this source http://xjsunjie.blog.51cto.com/999372/1734698

Forced handling of VM virtual machine not restarting shutdown