Conversion of running VM

[jamboy201]

Hello! We are converting a running VM that is running on ESXi 8 in a vCenter environment to HyperV.

The conversion seems to go fine and it takes a snapshot and runs the second pass and reports 100% complete. However, it does not power off the VM on the ESXi side. Any ideas of why it isn't turning it off once the snapshot has been copied over on the 2nd pass?

Thank you.

Jim

[yaroslav (staff)]

Welcome to StarWind Forum.
StarWind V2V does not shut down the VM by design. I will log it as a feature request. Thanks!

[coveyhappen]

The process of converting a VM from ESXi to Hyper-V involves several steps, and ensuring that the VM on the ESXi side is powered off is crucial for data consistency and integrity. Here are a few potential reasons why the VM might not be powering off after the conversion process reports 100% completion:

1. Permissions Issue: The account used for the conversion might not have the necessary permissions to power off the VM. Ensure that the account has sufficient permissions for VM operations, including powering off the VM.

2. Snapshot Issue: If there are issues with the snapshot taken during the conversion, it might prevent the VM from being powered off properly. Check for any snapshot-related warnings or errors in the task and event logs.

3. Conversion Tool Configuration: Double-check the settings in the conversion tool to ensure that the option to power off the source VM after conversion is enabled. Some tools have this as an optional setting that needs to be explicitly set.

4. Stuck Tasks: There could be tasks in vCenter/ESXi that are stuck or pending which can prevent further operations on the VM. Check the recent tasks in vCenter to see if any tasks are hung.

5. Script or Automation Errors: If the conversion process uses scripts or automation, there might be errors or missed steps in the script. Review any logs or output from the conversion tool to identify potential issues.

6. Hyper-V Conversion: Sometimes, the Hyper-V conversion might complete, but there could be post-conversion scripts or steps that are not executing as expected, which could prevent the VM from being powered off on the ESXi side.

To troubleshoot the issue further, you can:

- Review vCenter and ESXi logs to identify any errors or warnings related to the VM power-off process.
- Check the conversion tool's logs for any errors or warnings during the process.
- Manually attempt to power off the VM to see if it encounters any issues.
- Verify the permissions of the account used for the conversion to ensure it has the necessary rights.
- Ensure that there are no active tasks or snapshots that might be preventing the VM from being powered off.

By systematically checking these areas, you should be able to identify the root cause of why the VM is not being powered off after the conversion process.