@robertblissitt yup, afterward this seems to be a good best practice...
my hosts were up for 4 month, and because of DNS resolution problem had 77 patches to catch up (80 for one with advanced telemetry enabled)
a rolling reboot would have probably put in front the initial migration/evacuation problem (and subsequent zombies VMs)
and no patches applied, and no pool in a semi upgraded state
note to my future self, try a rolling reboot first.
vm boots with no issues after retying migration with Windows 10 template.
Maybe there can be checks put in place to not apply vtpm with bios is selected? Going forward will make sure to select the current os for the template not a newer version.
@olivierlambert so strange though. i have it enabled on 4 pools, that didn't propagte on hosts.
still VM boots up when not needed as explained on fist post of the thread.
i'll try différent combinations to see what's really going on
