VMM 2016 CU1 Bug - "Start VM after deploying it" not working
When I select "Start the virtual machine after deploying it" in the Migrate VM Wizard, the VM is not started. I have not tried powershell and I only have 1 install to test with. All Hyper-V targets are 2016 fully patched. Source hosts are 2012 R2.
Sure, please feel free to write to me (email@example.com) in case you see a repro.
Andy Bocko commented
The scenario I had was 2012 R2 standalone source host to 2016 cluster. I had to shutdown to do a storage migration due to incompatible processor. The VMs would never start in the cluster when i checked the "Start..." option. All of my hosts have been upgraded at this point. I will do a few more tests in the 2016 environment to see if i can repro.
We tried the below in our environment and everything worked fine for us, can you please share your specific repro-steps.
We tried the below with source and destination hosts running Windows Server 2016.
Scenario 1: Migrate a stopped VM from a clustered node to a stand-alone host. (Select Start VM after deploying it option) - VM started fine.
Scenario 2: Migrate a running VM from stand-alone host to a cluster node -VM was running after migration
Scenario 3: Migrate a stopped VM from stand-alone host to a cluster node (Select Start VM after deploying it option) - VM was running after migration
Scenario 4: Migrate a stopped VM within two cluster nodes (Select Start VM after deploying it option) - VM was running after migration
Can you please also specify the Guest OS running on the VM. Please feel free to reach out to me at firstname.lastname@example.org and we can take this offline.
Hi Andy, thanks for reporting the issue, we are looking into it and will update you more.