This article describes the necessary steps to enable detailed logging and collect essential data for troubleshooting quiescing failures in Windows virtual machines.
Before starting the data collection process:
Verify VMware Snapshot Provider Service
Ensure it is installed.
Confirm it is set to Manual start-up mode or is currently in the Running state.
Verify Microsoft Virtual Disk Service
Ensure it is set to Automatic start-up mode.
Confirm it is currently in the Running state.
If either service is missing or not in the required state, correct the configuration and retry the quiescing operation.
If the above checks are in place and quiescing still fails, proceed with the steps below to enable detailed logging and collect relevant data:
1. Enable Debug Logging for VMware Tools
Refer to the article on Enabling debug logging for VMware Tools within a guest operating system
2. Disable Log Throttling in VM Configuration
VMware Tools debug logging can generate extensive logs. To ensure no throttling limits the logs written by the hypervisor, adjust the VM configuration by editing the .vmx
file.
Method 1: Using vSphere Client (GUI)
Power off the VM.
Access the datastore where the VM is located:
From the vSphere Client, right-click the VM and select Browse Datastore.
Navigate to the VM's folder.
Download the .vmx
file to your local machine.
Edit the .vmx
file using a text editor (e.g., Notepad++).
Add the following line at the end of the file:
Save the file.
Upload the modified .vmx
file back to the VM’s datastore, replacing the existing file.
Right-click the VM in the vSphere Client and select Remove from Inventory.
Browse the datastore, right-click the modified .vmx
file, and select Register VM.
Power on the VM.
Method 2: Using ESXi CLI (SSH or ESXi Shell)
SSH into the ESXi host or open ESXi Shell.
Locate the VM's folder on the datastore:
Verify the VM's .vmx
file exists:
Create a backup of the .vmx
file (optional but recommended):
Edit the .vmx
file using vi
or nano
:
Add the following line at the end of the file:
Save the file and exit the editor.:wq!
Reload the VM configuration:
Note:
You can also perform a vMotion to another ESXi host to pick up the configuration changes if a VM restart is not immediately possible.
3. Reproduce the Quiescing Failure
Attempt to reproduce the quiescing operation failure.
4. Collect Required Logs and System Information
In the guest OS, run the following commands to collect the VSS state:
vssadmin list writers
vssadmin list providers
Collect the System and Application Event Logs:
Open Event Viewer.
Navigate to Windows Logs > System.
Right-click and select Save All Events As....
Repeat for Application logs.
Collect an ESXi log bundle from the host where the VM resides.
Ensure that after troubleshooting, the debug logging and log throttling configurations are reverted to their default state to avoid unnecessary log growth and system resource usage.