1. Compliance Error when Applying Host Profiles
Issue:
Applying Host Profiles to a host fails with the following errors:
- Specification state absent from host: device ‘<datastore>’ state needs to be set to ‘on’
- Host state doesn’t match specification: device ‘<datastore>’ needs to be reset
- Specification state absent from host: device ‘<datastore>’ Path Selection Policy needs to be set to ‘VMW_PSP_FIXED’
- Host state doesn’t match specification: device ‘<datastore>’ Path Selection Policy needs to be set to default for claiming SATP
Analysis:
This is caused by the PSA (Pluggable Storage Architecture) component.
Solution:
- Right-click Host Profiles and select Enable/Disable Profiles configuration option.
- Expand “Storage Configuration” and then expand “Pluggable Storage Architecture”.
- Uncheck “PSA Device Configuration”.
- Expand “Native Multi-Pathing (NMP)” and then expand “PSP and SATP configuration for NMP device”.
- Uncheck “PSP configuration for” and click OK.
2. Resolving VM/Storage Performance Degradation and High VM Disk Latency Due to IOPS
Issue:
- Low VM performance.
- High disk latency during backups.
- High vmdk disk latency.
Analysis:
These issues are usually due to insufficient IOPS (Input/Output Per Second) for the VM or IOPS below 30.
Solution:
- Understand what IOPS is: IOPS is a critical metric for measuring disk and storage performance. Higher IOPS can significantly improve system performance.
- Calculate the IOPS for each VM: Determine the total IOPS available from the storage and divide by the number of VMs to get the IOPS per VM.
- Account for additional IOPS consumption during backups, and use tools like I/O meter to test IOPS if necessary.
3. VM Fails to Power On Due to Missing or Locked Files
Issue:
- VM fails to power on.
- Errors encountered include:
- Unable to open Swap File.
- Unable to access a file since it is locked.
- Unable to access Virtual machine configuration.
- /var/log/vmkernel contains warnings about swap file lock and initialization failures.
- Errors connecting to the VMX file.
- VM hangs at 95% during power on.
- New VM deployed from template cannot be powered on.
- Console power status conflicts reported between vCenter Server and ESXi/ESX host.
Analysis:
The issue is often due to file corruption or locked files. Common VM files include:
- *.vswp
- *-flat.vmdk
- *-delta.vmdk
- *.vmx
- *.log
Solution:
- Identify locked files:
- Use vSphere Client to log into the ESXi/ESX host or vCenter Server.
- Locate the VM in the datastore.
- Check vmware.log for errors.
- Delete locked files:
- Use
vmkfstools -D /vmfs/volumes/<UUID>/<VM directory>/<locked file>to report the MAC address. - Check /var/log/vmkernel for the host locking the file.
- Use
4. Storage vMotion Fails with “CBTMotion” Error
Issue:
- Storage vMotion fails.
- Error message: A general system error occurred: Storage VMotion failed to copy one or more of the VM’s disks. Please consult the VM’s log for more details, looking for lines starting with “CBTMotion-“.
- /var/log/vmware/hostd.log contains similar error messages.
Analysis:
This is likely due to the VM’s hardware version being too old.
Solution:
Power off the VM, right-click and select Upgrade Virtual Machine Hardware.
5. Adding LUN Results in HostDatastoreSystem.QueryVmfsDatastoreCreateOptions Error
Issue:
The system scans the Devices LUN but fails to add it, displaying the error: HostDatastoreSystem.QueryVmfsDatastoreCreateOptions.
Analysis:
This issue is usually due to the LUN size being too large. VMware ESXi/ESX Server supports a maximum LUN size of 2TB-512Byte.
Solution:
- If the LUN is already set to 2TB, adjust it to around 1.88TB and try again.
- For new LUN planning, strictly follow official documentation and design parameters, recommending around 1.88TB per LUN.
6. vCenter Converter Fails to Push Agent: Converter Agent Installer/Uninstaller Failed
Issue:
- vCenter Converter fails to push the Agent to Windows Server 2003.
- Error message: Converter Agent installer/uninstaller failed on ‘xxxxxxxxx’.
- converter-server.log contains similar errors.
Analysis:
Possible causes include:
- Port 445 not open.
- Previously installed and uninstalled Agent.
- Windows Server service not started, causing IPC$ connection failure.
- Firewall blocking.
Solution:
- Ensure port 445 or NetBIOS protocol is operational.
- Disable the firewall during the conversion.
- If the issue persists, use Converter Standalone version or Converter CD for cold cloning.
7. Insufficient Datastore Heartbeating When Enabling HA in vSphere 5.0
Issue:
Configuring HA for ESXi 5.0+vCenter 5.0 results in insufficient Datastore Heartbeating error.
Analysis:
vSphere 5.0 HA has been rewritten to include Datastore Heartbeating for network partition heartbeat support.
Solution:
- Add more storage for heartbeat detection, or
- Ignore the issue by adding the parameter:
- Log into vCenter Server 5.0 via vSphere Client.
- Right-click HA Cluster, select Edit, and add the parameter
das.ignoreinsufficienthbdatastore. The default value is false.
8. “Updating” Issue When Logging into ESXi Host via vSphere Client
Issue:
Logging into vCenter Server 4.1 via vSphere Client is normal, but logging into ESXi host results in an “Updating” prompt.
Analysis:
The client needs updating via ‘vSphereclient.vmware.com’, indicating an issue with the client version.
Solution:
Install a higher version of the vSphere Client.
9. Red Flag 32-bit Linux “udevu” Error Prevents System Entry
Issue:
System entry is blocked by a “udevu” prompt, requiring Ctrl+C to proceed.
Analysis:
Virtual machine driver issues are suspected since the issue does not occur on physical machines.
Solution:
Download and install the latest VMware tools from the official website to resolve the issue.
Stay tuned for a sequel to the VMware vSphere Common Issues Summary!