天丫

You are experiencing these issues:

• You cannot power off an ESXi hosted virtual machine.
• A virtual machine is not responsive and cannot be stopped or killed. 

0. Connect VMware Infrastructure (VI) Client to VMware VirtualCenter Server.
0. Right-click on the virtual machine and click Power off.
0. Connect VI Client directly to the ESXi host.
0. Right-click on the virtual machine and click Power off.

If this does not work, you will need to install the Remote Command-Line Interface (RCLI) or vMA tools.

Installing the Remote Command-Line Interface tool

The Remote Command-Line Interface (RCLI) is used for the parts of this article. Ensure that it is installed before you proceed.

For ESXi 3.5 hosts, see Remote CLI Installation and Execution in the Remote Command-Line Interface Installation and Reference Guide.

Using the ESXi command line tool to power off the virtual machine

This procedure uses additional ESXi command line tools. Attempt each process before proceeding to the next, as they are listed in order of potential impact to the system if performed incorrectly.

0. On the ESXi console, enter Tech Support mode and log in as root. For more information, see Tech Support mode for Emergency Support (1003677) or Using Tech Support Mode in ESXi 4.1 (1017910). 
0. Get the World_ID with the command:
   
   # vm-support -x
   
   
0. Kill the virtual machine by using the following command in the home directory of the virtual machine.
0. • For ESXi 3.x, run the command:
     
     # vm-support -X <World_ID> -f –w <dir>
     
     where
     
     -f allows you to force vm-support to use a VMFS working directory.
     -w sets the working directory used for the output files. This is the directory where vm-support saves its final .tar archive. If this option is not specified, the working directory will be the directory from which vm-support is run.
     
   • For ESXi 4.x:
     
     # vm-support -X <World_ID> –w <dir>
     
     Note: If the vm-support command is slow with the -X switch, add -d0 to speed up the process.

Using alternate ESXi command line methods to power off the virtual machine

0. On the ESXi console, enter Tech Support mode and log in as root. For more information, see Tech Support mode for Emergency Support (1003677).
0. To list all running virtual machines and their corresponding VMIDs, run the command:
   
   vim-cmd vmsvc/getallvms
   
0. Power off the virtual machine using the VMID found in Step 2 and run:
   
   vim-cmd vmsvc/power.off <vm id> for ESXi 3.5 and 4.0
   vim-cmd vmsvc/power.off <vmid> for ESXi 4.1

Using the ESXi command line method to kill the virtual machine

0. To determine if the virtual machine process is running on the ESXi host, run the command:
   
   # ps | grep vmx
   
   On an ESXi 3.x host, if the .vmx process is running, the output appears similar to:
   
   ps|grep vmx
   7662 7662 vmx                        /bin/vmx
   7667 7662 vmx                        /bin/vmx
   7668 7662 mks:VMtoKill               /bin/vmx
   7669 7662 vcpu-0:VMtoKill            /bin/vmx
   
   On an ESXi 4.0 host, if the .vmx process is running, the output appears similar to:
   
   ps |grep vmx
   7662 7662 vmx                        /bin/vmx
   7663 7662 mks :VMtoKill              /bin/vmx
   7664 7662 vcpu-0:VMtoKill            /bin/vmx
   
   The parent process ID (PID) for this process is in bold. In this example, the PID is 7662. Several rows are returned, but you must make sure you identify the parent process. The first column contains the PID, and the second contains the parent's PID. Ensure you terminate only the parent process. Take note of this number for use in the following steps.
   
   Caution: Ensure that you identify the line specific only to the virtual machine you are attempting to repair. If you continue this process for another virtual machine the one in question, you can cause downtime for the other virtual machine.
   
   
0. If the .vmx process is listed, it is possible that the process has runaway and must be stopped manually. To kill the process, run the command:
   
   # kill <PID>
   
   
0. Wait 30 seconds and check for the process again.
0. If it is not terminated, run the command:
   
   # kill -9 <PID>
   
   
0. Wait 30 seconds and check for the process again.
0. If it is not terminated, the ESXi host must be rebooted to clear the process. This is a last resort option, and should be attempted only if the preceding steps in this article are unsuccessful.