I downloaded the Windows 10 1809 and Server 2019 ISOs the day they became available so I can start working on my templates.
I built the templates with EFI, paravirtual for the C drive and vmxnet3 adapter. I've been using this combo for other versions of windows 10/8/7and windows server 2008r2/2012r2/1016 without issue.
So far Windows 2019 (with desktop experience) seems to be ok at least for a basic vm and guest customization. Haven't tried anything else yet.
Windows 10 1809 on the other hand is very, very slow to reboot after the initial install or even just rebooting after making some changes post install. After installing the OS it took 10-15 minutes for the initial windows setup stuff (user, security settings, etc) to appear . I tried a VM set to BIOS and it seemed faster but was still quite slow. Server 2019 and other versions of windows 10 have no issue.
The hosts are esxi 6.5 and 6.7.
I haven't had a chance to try every combo of BIOS/EFI/vmxnet3/e1000e/paravirtual/lsi sas to see if one is the cause of the issue but was wondering if anyone else had noticed any issues or if it was just me?
We just upgraded to ESXi 6.7 to Update 3 - I can confirm this fixed the WIndows 1809 slow boot problem. We have a floating pool of 75 VM's for a single class, and it took 70 minutes for the pool to recompose yesterday. After the upgrade, it now took 12 minutes. I observed roughly a 7 minute boot time before, now its just over a minutes. Still slow in my book, the next step is to convert to the WIndows 10 1809 with our own customizations to remove bloat - and to switch to the windows 10 1809 for virtual desktops version. Has anyone tested the 1809 for virtual desktops version in their envrionment? I would just assume its 1809 with less bloat. (aka services that are not needed and slow it down)
anyone seening problems with w10 1809 blue screen'ing on restart? it takes about 5 minutes (random vm's) sometimes when i issue a restart. upgraded all hosts to 6.5u3, the vm's were not re-created, not sure if this matters or not. i run citrix xendesktop so the vm's are not re-created on restart / shutdown as i believe they are in horizon. eventually they do reboot, but it takes about 5 mins, startup is about 90s i'd say, not exactly fast, but not too slow either. storage is all ssd array
PS - this is the bsod error driver power state failure
I,ve upgarde mine vca an a esxi host to 6.7u3, and place an windows 2016 server om it.
When i shut down this vm it takes log (5 minutes) before vcneter shows the status poweroff.
And when i start this vm through vcenter, it takes more than5 minutes before the system starts.
i'am using chrome en the html5 vsphere client.
All mine storage is on iscsi vmfs6 volumes.
is this a bug with esxi6.7u3 and windows servers?
i put the vm (Windows 2016 server) back to mine old cluster(esxi6.7u1b) and it start and stop very fast.[vcenter=6.7u3]
i think this is a bug in 6.7u3 for windows 2016 servers.
any help or idea is welcome.
We see the same BSOD error message on ESXi 6.0 U3 hosts with VMware Tools 10.3.10 and Windows 10 1809.
If I understood Horizon support correctly the vCenter team are aware of the problem, I will probably open a SR to confirm this.
It seems VMware Tools 11.0 might have fixed the BSOD issues. So far no BSOD with fully patched Windows 1809 build, and numerous reboots.
I was wrong... Got BSOD with the Driver Power State Failure message after deploying a new VM from the template I made, with Guest Customization (sysprep).
VMware debugged the minidump, and it was a known issue that was fixed in VMware Tools 11.0.0.
Since I was still getting BSOD, I edited the VM and removed the USB Controller (3.0) and now I don't get a BSOD. I've asked VMware to confirm if this can be fixed.
VMware confirmed there is an issue with VMware Tools 11.0.0, USB Controller (3.0) and Windows 10 1809.
"removed the USB Controller (3.0) and now I don't get a BSOD. I've asked VMware to confirm if this can be fixed.
Update4: VMware confirmed there is an issue with VMware Tools 11.0.0, USB Controller (3.0) and Windows 10 1809.
Did you add a USB 2.0 controller? or just go without one?
Funny, I'm running tools v11, 1809 ltsc, usb 3.0 and not having any issues at all, perhaps it is only with new deploys or something? tools v11 did fix the logoff issues for me though as the notes state, along with tools crashing every 7 days or so
I was looking for this in virtual center release notes, but as the PR mentioned, it is for ESXi release notes. hmm. Guess i have to update virtual center first just to follow best practice, then esxi. Thanks for the info.
As previously mentioned, I can confirm with my environment with hosts upgraded to ESXi 6.7 U3 this is indeed resolved:
PR 2287232: 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.
I have windows 10 1903 vm's. Built on vmfs 6 storage. vm hardward 15, tools 10.3.10 or 11.0. Multiple snapshots. No delays in widows boot time. Instant Clone deployments work perfectly fine.
Same problem here:
VMware ESXi, 6.7.0, 13981272
Storage connected via fiberchannel
Windows 1803 with snapshots: normal boot
Windows 1903 with snapshots: slow boot
I am having similar problem. Anyone help me out.
Answer from VMware support:
Would it be possible to follow the workaround reported in the KB article ( https://kb.vmware.com/s/article/67426 )
Also as per KB article this issue should be fixed in 6.7U3.
Upgraded to the last version.
Did notice a change. That change is reduce in 10-20% that is it. Apparently workaround at first instance- Because when the system boots, it take at least another 10 seconds to bring up VMware tools.
We are moving to W1803. It is so sad.