Virtual Maschine does not Start after Migration from Classic IAAS with Azure Resource Manager

marczinser 20 Reputation points
2023-02-02T08:03:07.01+00:00

Hello,

we have a migrated one of our classic IAAS VMs on Azure to the new Resource Manager. After the pre-check everything seems to work as expected. A few seconds later we received an error message.

After this we have now two VMs on Azure. The old and the new one. Both can't be started. If we try to start the new VM we can see the message that there is an ongoing migration. But Wochenende can't see any status of the migration process wether the process is still ongoing or the process died. Is there anything Wochenende can do at the moment or can we restart the process?

The initial VM is also not really big. It has a HDD Volume from about 150GB which in my opinion should not take this much to migrate.

Wochenende started the migration yesterday afternoon and waited until now which should be more than 12 hours.

Thank you for your help!
Regards, Marc

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,849 questions
Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
795 questions
0 comments No comments
{count} votes

Accepted answer
  1. Prrudram-MSFT 24,456 Reputation points
    2023-02-02T09:15:07.6866667+00:00

    Hello @marczinser

    Thank you for reaching out to the Microsoft Q&A platform. Happy to answer your question.

    I have dealt with a similar issue recently with a user on Microsoft Q&A on this thread https://learn.microsoft.com/en-us/answers/questions/1160767/unable-to-access-original-or-migrated-vm-after-att where technical support investigated the issue and walked through the corrective actions.

    I see you are in a situation, where both the VMs original and migrated are inaccessible. We won't be able to abort this migration as rollback is not supported after the resources have been successfully migrated through the commit operation but stuck somewhere.

    Right thing to do at this point is to contact Azure VM technical support team and have this issue debugged at the deeper level. If you don't have an active support plan or do not have the ability to open a technical support ticket, please let me know I can help you further on this.

    Ref: https://learn.microsoft.com/en-us/azure/virtual-machines/migration-classic-resource-manager-ps

    Hope this helps!

    If you have any further questions at all, please let me know in the comments.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.