There is a situation, when in VMware vSphere Client VM on ESXi does not obey commands Shut Down / Power Off and remained “unresponsive” to you. The following describes the same three ways to “kill” the unruly virtual machine, but only as to the VMware ESXi.

1. Because the service console in VMware ESXi is not formal, we can use a special remote management tool VMware vSphere CLI , which allows access to the ESXi interface from the command line. It can be installed as a framework for Windows and Linux, and manage ESXi via script, and you can use ready-made virtual machines with this interface, called vSphere vMA.

Once put vMA, type the following command to list the VMs on the host VMware ESXi with paths to configuration files:

vmware-cmd.pl-H <ESXi host name>-l

Then type the following command in the console vMA for output of the virtual machine with the specified path to the vmx-file on the host ESXi:

vmware-cmd.pl-H <ESXi host name> <VM config file path & name> getstate

Next, type the following command to stop the virtual machine:

vmware-cmd.pl-H <ESXi host name> <VM config file path & name> stop hard

Check the status of the virtual machine with the previous command, and if does not work, go to the next method.

2. In fact, as many know, kind of service console in BusyBox in VMware ESXi, is still there. Therefore, enter into it like this way:

• In the console, VMware ESXi host, press ALT-F1
• Print Unsupported (text, you will not see), you will enter Tech Support Mode , and will require a password. Enter a password for the user root
• Will prompt for the ~ # .

Now execute the following command:

vm-support-x

For a list of virtual machines and their identifiers (VMID). After that, turn off the virtual machine with the specified identifier following command (it will create a dump with debugging information in the swap section of ESXi, by using the -w <vmfs volume path> can specify VMFS-volume and folder in which to put the dump):

vm-support-X <VMID>

Then re-check the state of the virtual machine command: VM-Support-x

3. If this does not help, then we must directly try to kill the process that implements a virtual machine for ESXi. To do this, again go into the “service console” as in the preceding paragraph and type the command:

ps-g | grep <virtualmachinename>

Further search process group ID (process group ID, PGID), which is in the fourth column of the results output. Next, kill the processes with a virtual machine running:

kill -9 <PGID>

Again, check the state of the VM, which should already be turned off, a team of VM-Support-X .

Veeam, a well known provider of solutions for managing virtual infrastructure VMware, released version of Veeam nworks Smart Plug-in 5.6 product for VMware vSphere. This product is part of Veeam ONE, which allows for a comprehensive monitoring infrastructure of VMware vSphere Virtual Servers under the control of HP Operations Manager.

New features Veeam nworks Smart Plug-in 5.6:

• Support for HP Operations Manager for Linux (OML). Now nworks portfolio includes support for all versions of HPOM – for Windows, Unix and Linux.

• Monitoring the compression of memory VMware vSphere (Technology Memory Compression in VMware ESX 4.1)

• Track delayed treatment to storage (Disk queue latency) – to identify bottlenecks in the disk storage subsystem of virtual machines on VMFS volumes

• Monitoring the duration of storage snapshots (snapshots) – for notifying administrators of potential problems.

From the new VMware users we often hear the question of how to enable access via SSH to the server console, VMware ESXi (this mode is called Remote Tech Support Mode). I must say that the server console: VMware ESXi is built on a BusyBox package, which allows you to perform a certain set of nix-teams, and the console itself is not meant to replace the Service Console of VMware ESX. Since the fifth version of VMware vSphere will contain only ESXi, ESX hypervisor itself and cease to exist, users are encouraged to use the interface of VMware vSphere Management Assistant for the centralized execution of scripts on the servers of VMware ESXi.

So how to include SSH access to VMware ESXi. It can be activated in two ways:

• Directly from the VMware ESXi server console
• From the VMware vSphere Client connecting to ESXi server

1st Way – Enabling SSH from the ESXi server console.

1. Open VMware ESXi Server console and press <F2> key .

2. We turn to the Troubleshooting Options:

3. Enables or disables SSH access to VMware ESXi (Remote Tech Support Mode).

Please note that there is also a Local Tech Support Mode – is access to the physical server console for VMware ESXi directly nix-execution of commands.

2nd Way – Enable SSH for ESXi from vSphere Client.

1. Connecting to the host via VMware ESXi vSphere Client in the Configuration tab and go to subcategory Security Profile in category Software.

Click Properties:

2. We can see a list of services included for VMware ESXi. It is evident that Local Tech Support and Remote Tech Support (available on SSH) enabled. Press the Options button for the selected services – Remote Tech Support (SSH).

3. Choosing a policy to start the service (either manually or automatically) and run the service SSH, by clicking Start.

To manage theVMware ESXi server via SSH use Putty.