Has anyone tried 1903 to see if it's the same issue?
I don't see any information about vSphere 6.0 update 3 or any other build versions of 6.0. Can anyone chime in if this Build 1809 problem is happening on 6.0u3 and/or specific builds of 6.0u3?
The problem happens with VMFS 6 and that's only supported as of vsphere 6.5. If you're still on vsphere 6.0 then you're running VMFS5 so you should be ok....
Answered my own question.... It's still an issue in 1903. Blank OS boots up in 15 seconds. Added one snapshot and it went up to 1 minute 45 seconds. Didn't bother building an image with it.
Glad to see there is a lengthy thread on this, I thought I was just losing my mind. For the record, migrating the VM to another data store and then consolidating does seem to have improved boot times significantly. I'll have to keep this in mind when we recompose in the future as a temporary workaround rather than sitting on my hands for half an hour for the VM to start.
Start of VMs with Windows 10 version 1809 running on snapshots on VMFS6 takes a long time and Without snapshots there should be no performance problems.
Workaround is to use VMFS5 or NFS Datastore. Issue to be fixed in a future ESXi release for 6.5 and 6.7 (Q3 2019) .
Thanks, this is helpful to know - we're using Win10 1809 still, with VMFS5 and vSphere 6.7 U1, and still have the horrible boot slowness. a Full Win10 VM boots just fine, but the moment you take a snap or provision linked-clone VM's from that initial VM, the boot times on those linked clones are 15-30 minutes, every time you restart one of them.
I can confirm, this is still not working correctly with Windows 10 1903 and all the latest updates for Esxi 6.7 with VMFS 6, completely unusable.
Same problem here:
VMware ESXi, 6.7.0, 13644319
Storage connected via fiberchannel
Windows 1803: normal boot
Windows 1809 with snapshots: slow boot
Linked Clones (and golden image) with Windows 1809: slow boot
It is a very annoying situation that VMware let's its customers down in this case :-(
We created a datastore VMFS5 and it soon solved the problem. Any prediction of vSphere 6.7 U3?
Issue to be fixed in a future ESXi release for 6.5 and 6.7 . ETA might be (Q3 2019) .
1 person found this helpful
Not sure what is different on mine but I created a VMFS 5 data store and composed a new set of VMs on this data store but have not noticed any significant difference in boot times (Win 10 1803). Still seems to hang for upwards of 20 minutes just spinning at the Windows splash screen.
Thanks for this info - exact same issue we're experiencing. Doesn't matter if it's Win 10 1803, 1809, or 1903 - VMFS5 of VMFS6, using Pure Storage or vSAN. I also completely left out Horizon and just composed a Win10 VM in vSphere from a template, and THAT helped. It seems if you create all dedicated Win10 VM's from a template (which won't have associate snaps) the issue is fixed, but that's only a workaround (if you have the host resources).
So 6.5u3 dropped, however i still don't see this fixed in the resolved section, anyone else?
I see this in the release notes which seems like the issue in question:
PR 2292798: Virtual machines with Microsoft Windows 10 version 1809 might start slowly or stop responding during the start phase if they are running on a VMFS6 datastore
If a virtual machine is with Windows 10 version 1809, has snapshots, and runs on a VMFS6 datastore, the virtual machine might either start slowly or stop responding during the start phase.
This issue is resolved in this release.
We installed 6.5 U3 (Build 13932383) today and all VDI desktops feel snappier. Overall feeling with me and my colleagues is that this update also improved performance for us.
Our floating desktops are stored on local VMFS 6 SSD storage.
We were not affected by the slow boot issue so i can't say if this update indeed fixed that.
Edit: we did some measurements and logintimes on average dropped from about 30sec to 20sec!