vProgression

Learn by doing.......

  • About
  • Blog
  • Contact

Connect

  • LinkedIn
COPYRIGHT © 2017

Windows Server 2012 Fail Upon Reboot – VM Hardware V10

12/14/2015 By vprogress Leave a Comment

Thinking

Recently, I ran into an issue where servers running Windows 2012 Server R2 hardware version 10 would fail on reboot in our virtual infrastructure. There is a workaround to fix this issue without having to rollback to hardware version 9 if you are not in a position to upgrade to VMware ESXi 5.5 Update 3 or VMware ESXi 6.0 for that matter.

To work around this issue, you can do two things:

Add monitor_control.enable_softResetClearTSC = TRUE to the VM configuration parameters which applies the setting to the VM individually.

or

Add echo ‘monitor_control.enable_softResetClearTSC = “TRUE”‘ >> /etc/vmware/config to the host, which will apply this fix to all VMs running on the host.

IMPORTANT: You should NOT apply this at the host level if you are using Solaris VMs as there could be unexpected results such as; Solaris VMs hanging.

I will walk through the steps below to apply the setting at a VM level.

  1. Log into vSphere Client
  2. Right-click the virtual machine and click Edit Settings to open the Virtual Machine Edit Settings window.
  3. Click VM Options. Select General, then Configuration Parameters.

 

Config_Parameters

4. Click Add Row.

Config_Add_Row

5. Add monitor_control.enable_softResetClearTSC = TRUE

Config_Line_Click_Ok

 

 

 

 

 

 

 

 

Share this:

  • Click to share on Twitter (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)
  • More
  • Click to share on Facebook (Opens in new window)
  • Click to share on Google+ (Opens in new window)

Filed Under: VMware Tagged With: Images Right

VMware Services Fail to Start after applying 5.5 U2E or VIMPatch-5.5.0-2646481-20150401

11/03/2015 By vprogress Leave a Comment

In my first post, I will discuss an issue I ran into while remediating a Java security vulnerability for vCenter. Below are the steps that were taken to correct the issue regarding VMware services failing to start after the update.

IMPORTANT:  The only update between vCenter Server 5.5 U2d and vCenter Server 5.5 U2e is an updated JRE Build to patch JRE security vulnerabilities. Using the following workaround will not change the vCenter Server 5.5 Build Number. It will continue to display Build 2442329. The same would occur if you successfully applied VIMPatch-5.5.0-2646481-20150401. This is by design as the vCenter Server binaries are not changing.

  1. Backup or Take a snapshot of the vCenter Server machine.
  2. Stop the following VMware Services:
  • VMware vSphere Web Client
  • VMware Log Browser
  • VMware vSphere Update Manager Service
  • VMware Profile-Driven Storage Service
  • Vmware VirtualCenter Service
  • VMware VirtualCenter Management Webservices
  • VMware vCenter Orchestrator Server
  • VMware vCenter Inventory Service
  • VMware Secure Token Service
  • VMware Identity Management Service

3. Confirm that no java.exe process is running via an elevated command prompt:

tasklist | findstr java

4. From the Windows Control Panel > Programs and Features, uninstall the VMware vCenter Server – Java Components.

5. Confirm that the directory C:\Program Files\Common Files\VMware\VMware vCenter Server – Java Components is completely removed. Rename the folder if it still remains.

6. Mount the vCenter Server 5.5 U2e installation media.

7. Browse the media to “Media\vJRE\”

8. Launch the VMware-jre.exe and complete the installation accepting all defaults.

Note: The VMware vCenter services will be started automatically by the VMware-jre installer.

Share this:

  • Click to share on Twitter (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)
  • More
  • Click to share on Facebook (Opens in new window)
  • Click to share on Google+ (Opens in new window)

Filed Under: VMware

  • « Previous Page
  • 1
  • 2

Search

Recent Posts

  • UnityVSA Deployment to ESXi Host (Part 1) 09/07/2017
  • Update ESXi 5.0 to ESXi 5.5 via CLI 03/17/2016

Archives