VMware:- How to remove a locked VM

-

Removing the Lock:


Power off the virtual machine holding the lock
Reboot the ESXi host that holds the lock

Removing the .lck file (NFS only)
Power down the virtual machine and remove lck-#### files in the virtual machines directory.
Caution: Only remove the lck files of a powered off virtual machine
Note: VMFS volumes do not have lck files. The locking mechanism for VMFS volumes is handled within VMFS metadata on the volume.

If above steps not removed the lock please follow below steps.

Enable SSH access to the ESXi host where problematic VM reside
Type below command
esxcli vm process list
This will list the VMs on the host and most importantly the VM’s World ID and its storage location of the VMX File.
After confirming that the VM is the one with the issue, you can power off the VM with the command:
esxcli vm process kill -t [soft,hard,force] -w WorldNumber
so for example:
esxcli vm process kill -t hard -w 123456789
NB.
Soft = Graceful
Hard = Immediate shutdown
Force = Nuclear option

Comments

Post a Comment

Popular posts from this blog

VMware:- Esxi Log File Locations

-
Enable SSH and connect the host through CLI tool-  *Authentication- /var/log/auth.log *ESXi host agent log - /var/log/hostd.log *Shell log - /var/log/shell.log *System messages - /var/log/syslog.log *vCenter Server agent log - /var/log/vpxa.log *Virtual machines - The same directory as the affected virtual machine's configuration files, named vmware.log and vmware*.log. For example, /vmfs/volumes/datastore/virtual machine/vmware.log *VMkernel - /var/log/vmkernel.log *VMkernel summary - /var/log/vmksummary.log *VMkernel warnings - /var/log/vmkwarning.log *Quick Boot - /var/log/loadESX.log *Trusted infrastructure agent - /var/run/log/kmxa.log *Key Provider Service - /var/run/log/kmxd.log *Attestation Service - /var/run/log/attestd.log *ESX Token Service - /var/run/log/esxtokend.log *ESX API Forwarder - /var/run/log/esxapiadapter.log
Read more

ESX and vCenter Alarms

-
Image
  Definition An  Alarms  is a   notification  that are activated in response to an event, a set of conditions, or the state of an inventory object. An alarm definition consists of the following elements in the vSphere Client: ·  Name and description - Provides an identifying label and description. ·  Targets - Defines the type of object that is  monitored. -  VM\  DataSore \N\W  etc. ·  Alarm Rules - Defines the event, condition, or state that triggers the alarm and defines the notification severity. It also defines operations that occur in response to triggered alarms. ·  Last modified - The last modified date and time of the defined alarm.   Alarm categories – Alarms have the following severity levels: ·  Normal –  green  -   Status is Good. The health of the object is Normal ·  Warning – yellow  -  Status is Warning – The Object experiencing Some Problem ·  Ale...
Read more

Convert VMware Snapshot into Memory Dump

-
Image
  Convert VMware Snapshot into Memory Dump Background   This document explains about generating a memory dump for a VMWare Virtual Machine when the machine becomes unresponsive. VM becomes unresponsive for various reasons, you may not be able to get into any OS related settings or access any application. Even users may get not be able to access any shares or resources of this machine.   In this type of situation Memory dump would be required to  analyze  the cause. Even if the OS is configured to generate a Memory Dump for System Crashes, it would not be able to generate a Memory Dump for System Unresponsiveness most of the  times. But  with a VMWare VM, you can take a snapshot of the machine when it is unresponsive and then use vmss2core.exe tool to convert the snapshot to a Memory Dump. The target audience for this information is any technician that is responsible for creating and deleting snapshot in the Levi virtualization environment.   Note ...
Read more