We have been noticing some alerts saying Virtual Machine is not responding when running a Virtual Machine level backup. Customers were complaining about the application unavailability and they were getting some alerts saying Virtual Machine is not responding or down state at the same time of everyday. This issue appeared due to the FREEZE operation on the file system.
We have tried several troubleshooting steps to find a solution for this and had to spent considerable amount of time on the same issue, unfortunately we were continuously getting the same “Virtual Machine is not responding” alert from the monitoring. Finally, we were able to find a solution after performing the below steps separately for Windows and Linux Virtual Machines.
Virtual Machine is not responding ? This is the workaround for the Linux Virtual Machines
Connected to the ESXi host which was running the affected Linux Virtual Machine and changed the directory to the Virtual Machine folder.
Checked disk.EnableUUID setting is in the .vmx file
/vmfs/volumes/<datastore>/<virtual_machine_folder>/#cat virtualmachinename.vmx | grep disk.EnableUUID
In my case this parameter did not exist, so I had to edited the .vmx file using a text editor, added the disk.EnableUUID parameter and set it as “FALSE”, if you can see the parameter in your .vmx file, set the value to “FALSE”. (I used “vi” editor and “:wq” used to save the parameter).
Confirmed the parameter addition using the same command
After the completion of the parameter addition logged in to the Operating system of the Virtual Machine and changed the directory to “/etc/vmware-tools/” folder and check whether there is “tools.conf” file is there, if it id not there then create a file. In my case we had to create the file.
#cd /etc/vmware-tools/ #/etc/vmware-tools/ls
To create the file used vi editor
Added the below content to the file, save it and exit
[vmbackup] enableSyncDriver = false [logging] vmtoolsd.level = debug vmsvc.level = debug vmusr.level = error vmvss.level = debug guestinfo.level = error vix.level = error vmsvc.handler=vmx vmbackup.level=debug vmbackup.handler=vmx
Virtual Machine is not responding ? This is the workaround for the Windows Virtual Machines
If it is a Windows Virtual Machine you might need to check the Windows Application logs to identify whether there are errors related to the VSS Writers. In some cases VSS Writers may having some issues and had to exclude the VSS Writers from the snapshot operation. A sample issue can be seen in this Microsoft article, you might be seen something similar to these symptoms.
To find the VSS Writers run a Command Prompt with the Administrative privileges and run the below command
C:\Windows\system32>vssadmin list writers
Read more about VSSAdmin Utility from Microsoft Documentation.
Then opened the “%ALLUSERSPROFILE%\Application Data\VMware\VMware Tools\” location in the explorer
Created a “vmbackup.conf” file, to do that opened a Notepad added the VSS Writer and saved it as a configuration file. See below screen captures for more information
Created the “tools.conf” file in the same location and added the below content
[logging] log = true vmtoolsd.level = debug vmtoolsd.handler = file vmtoolsd.data = C:\ProgramData\VMware\VMware Tools\vmtoolsd.log vmsvc.level=debug vmsvc.handler=vmx vmbackup.level=debug vmbackup.handler=vmx vmusr.level = error vmvss.level = error guestinfo.level = error vix.level = error
You should be able to see something similar to this after the creation of the file
Restarted the VMware Tools Service
After doing these configuration changes to the .vmx file and the .conf file of the affected Virtual Machines this issue was resolved and Virtual Machines are not freezing during the backup operation. I hope you will not be seeing “Virtual Machine is not responding” alert in your environment after following these steps.
If you found this post as useful please rate the post and share it!