Add the following line to the vmx file: monitor_control.enable_ softResetClearTSC = "TRUE" 3. This can be done a few ways: First method: Manually editing the VM's vmx file one VM at a time. Please note that this has not been tested extensively by engineering, and should be run at your own risk as it is just a workaround which has not been fully QE tested. This will basically tell the vmx file that the TSC for all vCPUs should be reset to zero on a soft reset of the machine, and not just CPU0. There is a workaround suggested from engineering to add a line of code to the vmx (configuration) file of the VM to prevent this from reoccurring. Our engineering team here are currently working on a code change to accommodate this. It does not reset the TSC of the other vCPUs and the resultingĭiscrepancy between two vCPUs' TSC can result in the OS not booting past the Windows splash screen, and a full power off and on will fix it. Starting with Windows 8 / Windows 2012 Server, during its boot process the operating system will reset the TSC (TimeStampCounter, which increments by 1 for each passed cycle) on CPU0. If anyone implements any of these changes, please let me know if it does or doesn't work. There is a bug with ESXi and their engineers are working on a fix. I have been on PTO this weekend where I work so I haven't been checking my email until this morning. And I know I will be battling more and more Windows 2012 R2 that fail their late night patching cycles as the weeks go by. There is definitely something wrong here. Will be watching this thread with interest.
#Vmware esxi 6 windows server 2012 r2 driver#
Its not my standard, but if it is a bug in the LSI driver it would get around it. It doesn't rule out latency but I just can't prove it.Īnother option I have considered, but haven't tried yet, is to replace the virtual LSI controller with VMware ParaVirtual. Theĭatastore latency went up to 160ms+ but the VM still rebooted just fine.
![vmware esxi 6 windows server 2012 r2 vmware esxi 6 windows server 2012 r2](https://www.jepeuxtoutexpliquer.com/wp-content/uploads/2017/02/2017.02.10-Lab.jpg)
I have moved a Windows 2012 R2 VM to a separate LUN that I then generated lots of I/Os against the LUN whilst I rebooted the VM. I 'suspected' this is to do with heavy I/O on the underlying datastores, but have not been able to prove it. Data Protection Manager does not need to runĪ consistency check over the volumes at next boot-up). They seem to be hanging very early in the boot cycle - early enough that the volumes (drives) are not marked as dirty when you 'reset' the VM (i.e.
![vmware esxi 6 windows server 2012 r2 vmware esxi 6 windows server 2012 r2](https://i0.wp.com/www.techcrumble.net/wp-content/uploads/2019/02/TC-W2k19-HCL-Check-0001.png)
I have so far not been able to track this one down. They hang at the spinning circle of dots on the boot screen. We have over 160 VMs, of which 25+ are now Windows 2012 R2 Servers.Īll VMs patch correctly, but a RANDOM PORTON of the Windows 2012 R2 servers fail to complete their boot after patching (6 last patching cycle). The windows VM servers are patched by WSUS with 4 different patching times/groups.
#Vmware esxi 6 windows server 2012 r2 update#
VMWare ESXi 5.5 Update 1 and Update 2 servers.