ESXI- how to use shell.log

Shell.log is the one of the log file which helps us to resolve problems and in some scenarios it will help us to do the audit process.

Example 1

  1. With the below example we can see that per-worker-01a vm is runnin on esx-01a.


In few hours later we can notified that vm has powered off. We could nt find any logs in vCenter or in the os level.

What we can do is we can check the shell.log file. If someone has powered off the vm using command line on the ESXi , we can find the details.


In the above shell.log file we can see that someone has tried to power off this vm.

Continue reading

How to use for loop to identify vmdk locked files

some times we are facing that vmdk locked scenario which we need to identify the locked file using vmkfstools.  But when we having multiple vmdk files, we need to run this command several times. To overcome this issue I have tried to use for loop in esxi shell. This may be help others when they having same problem.

for files in *.vmdk


>vmkfstools -D ${files}



vSphere 6.7 Quick boot


, , , , , , ,

vSphere 6.7 quick boot is new feature which is integrated with update manager. When we performing patching activities with earlier versions of vSphere most of the time we need to reboot the ESX hosts. This is very painful because normayy it will take more than 5 minutes to reboot hardware server. Also sometimes we may need to login using ILO\BMC\IDRAC and check the boot status.

With the version 6.7 we can configure quick boot of ESX hosts.This feature will allow us to reboot only the hypervisor without rebooting ESX’s hardware.

Requirements of this feature-

This feature will not work with all the hardware servers.we can follow below link to get the compatible hardware models.

Dell severs

HP Servers

How to check the compatibility of your server-

We can run


And check the compatibility of our server with quick boot.


How to configure this feature

1.login to your vCenter web client

Go to the update manager

Select Manage

Select Settings

Click on Edit


Enable quick boot


Now we are going to remediate one of my esx host.

From the target host we can see qucik boot is enable on this



I used VMware hol HOL-1904-01-SDC-HOL to test this feature

Reference links

Powershell script to get datastore names with mapped esx hosts & naa ids

Add-PSSnapin VMware.VimAutomation.Core

Connect-VIServer myvcenter1.test.local



foreach ($dstore in $dstores)



Write-Host $dstorename



$esx=get-datastore $|get-vmhost

$esxformat=(@($esx) -join ‘,’)

$naaformat=(@($naa) -join ‘,’)






$result=New-Object psobject -Property $properties

$result|select name,esxname,naaid|export-csv C:\Users\darshana\Desktop\ds.csv -Append -NoTypeInformation


Migrate vCenter 5.5 windows implementation to vCener 6.5 appliance


, , , , , , , , , , ,

First of all we need to run Migration Assistance tool from vCenter 5.5 server. To do this we can mount the vCenter 6.7 installation media to the computer.

Inside the ISO file we can locate migration assistance in the folder migration-assistant


This exe will prompt for sso admin password Continue reading

how to identify vmdk locked owner


, , , , ,

When we are trying to power on/vMotion/sVmotion virtual machines sometimes we may get vmdk locked errors. This can be due to one of the following reason.

  • Backup software has locked the vmdk file/s
  • Error of snapshot
  • Because of host failure multiple host tried to start the vm

How to we can release this lock file.

First we need to identify which host has locked this vmdk file.


With the below example we can use vmkfstools -D command to identify the host


This will show us the host’s management network’s mac address

Then we need to check all the host and find the mac address. In a small environment it’s not a big thing. But if your environment is large, then we need to have some alternative solution.

Vmfsfilelockinfo will help us on this requirement. We can use this command with few parameters. Then it will give the ip address or host name of the esx host which has locked that vmdk file