Virtual Machine already Moved from Hyper-V

  • 22 January 2024
  • 1 reply

Hello, I have tried to move a Windows 2016 server VM from Hyper-V to AHV. Move would not configure the move automatically because WinRM wasn’t running.

Manually installing the agent gave me the following:

Firewall: Inbound port [8087] is open

Service state: [Hyper-V Virtual Machine Management] is not running. Starting service…

Service install failed. Please check logs at [location]

The log:

Log file created at: 2024/01/22 08:50:30
Running on machine: reaper
Binary: Built with gc go1.18.10 for windows/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
E0122 08:50:30.724796   11652 service.go:396] Could not access service: The specified service does not exist as an installed service.
E0122 08:50:30.740733   11652 service.go:433] Service start failed for [vmms]

When I looked at the VM in Hyper-V there was a note saying that the VM had already migrated, so the target VM in Nutanix must have moved but the application clearly failed so we rolled back to the Hyper-V.

Is there a way to reset the virtual machine so that a migration can again be attempted? I am guessing that this would be doable but there’s some underlying problem with Hyper-V

This topic has been closed for comments

1 reply

Userlevel 5
Badge +6

I prefer to contact Nutanix support