Welcome back to the VMware vSphere Common Issues Summary series! It’s been a while, and we’re glad to have you back.
1. Installation Error on Win7 in View Desktop
Issue:
When installing software on a Win7 view desktop, you may encounter the error “System administrator has set policies to prevent this installation.”
Solution:
1. Open “Start -> Control Panel -> Administrative Tools -> Local Security Policy.” If “Software Restriction Policies” is not defined, right-click to create one. Then, double-click “Enforcement” and select “All users except local administrators.”
2. Run `gpedit.msc` from the Start menu. Navigate to “Computer Configuration -> Administrative Templates -> Windows Components -> Windows Installer.” Set the first option to either “Not Configured” or “Disabled.”
3. Delete the registry key `HKEY_CLASSES_ROOT\Installer\Products\4080110900063D11C8EF10054038389C` using `regedit` to resolve most issues.
2. Sustained High CPU Usage Solutions
Issue:
High CPU usage can indicate an optimal use of CPU resources, but sustained high usage may signify problems.
Solution:
1. Ensure VMware Tools is installed on all VMs.
2. Compare the CPU usage of the affected VM with others on the same host.
3. Check if the CPU ready time is due to CPU limits, and increase the limit if necessary.
4. Allocate more CPU shares or set a CPU reservation for high-priority VMs.
5. Increase the VM’s memory allocation to reduce I/O activity.
6. Reduce the number of virtual CPUs (vCPUs) if not all are needed.
7. Add the host to a DRS cluster, increase the number of hosts, or upgrade the physical CPU if needed.
8. Use the latest hypervisor version and enable CPU-saving features like TCP Segmentation Offload.
3. vMotion Failure
Issue:
vMotion fails with the error “A general system error occurred: Failed to flush checkpoint data!” due to VM settings like resolution and hardware version.
Solution:
1. Adjust screen resolution to below 1280×1024 or match it with the second screen.
2. Avoid upgrading the VM’s hardware version to 8.
3. Increase checkpoint cache size from 8MB to 16MB via VM settings.
4. Set `mks.enable3d` to TRUE in VM settings.
4. VirtualCenter Management WebServices Failure after Database Migration
Issue:
After migrating the vCenter Server database to a new host, the VirtualCenter Management WebServices may malfunction.
Solution:
1. Modify the database location in the `database_name.properties` file under the Tomcat Server’s configuration.
2. Update the database hostname or IP address in the file.
3. Restart VMware VirtualCenter Management WebServices or the entire vCenter Server.
5. Inability to Migrate Management Network to vDS in ESXi 5.0:
Issue:
Management network migration to vDS in ESXi 5.0 fails with the error “A specified parameter was not correct.”
Solution:
Ensure the network coredump feature is enabled. If necessary, disable coredump on the specific network card using `esxcli system coredump network set –enable false`.
6. VM Cloning Failure:
Issue:
Cloning a VM fails at 99% due to UTC clock desynchronization.
Solution:
1. Access Time Configuration in the vSphere Client and ensure time synchronization is correct.
2. Adjust NTP settings if needed and restart services.
7. Generating New ESXi Certificates:
Steps:
1. Backup existing certificates in `/etc/vmware/ssl`.
2. Run `/sbin/generate-certificates` to create new certificates.
3. Restart the `hostd` process with `/etc/init.d/hostd restart`.
4. Verify the new certificates by comparing timestamps.
8. Deleting Unused Plugins in vCenter:
(Additional steps or methods can be included as needed.)
9. VM Automatically Migrates After Cold Migration:
Issue:
A VM automatically migrates to another ESXi host after being powered on post-cold migration.
Solution:
This is due to DRS being set to Fully Automated. Adjust the automation level to Disabled or Manual in the DRS cluster settings to prevent automatic migration.
This concludes our VMware vSphere Common Issues Summary (Ⅴ). Stay tuned for more insights and solutions!