Share via

Prepare linux custom image and create VM with it?

Ibrahim Khalid 41 Reputation points
2022-01-13T09:25:29.147+00:00

I have a Debian base Linux distro in my on premises Hyper-V. I created vhd and upload it in my storage account. I also created custom image and when I want prepare VM with it this error showing:

Provisioning failed.
OS Provisioning for VM 'myvm' did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, make sure the image has been properly prepared (generalized).
* Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/
* Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/
* If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to shared image gallery. Please refer to https://aka.ms/movetosig for the same..
OSProvisioningTimedOut
ProvisioningState/failed/OSProvisioningTimedOut
Not Ready.
VM status blob is found but not yet populated.

Please help me regarding this issue.

Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. vipullag-MSFT 26,537 Reputation points Moderator
    2022-01-13T11:02:49.867+00:00

    @Ibrahim Khalid

    Thanks for reaching out to Microsoft Q&A Platform.

    There are several reasons for running into OS Provisioning Time out problems like Provisioning agent issues, Issue with the custom image, other potential host side or extension issue etc.
    Please make sure that all the steps in this document are followed correctly.

    Usually this Time Out error happens when the platform has not heard back within 40 minutes from the VM guest OS during provisioning of the VM.

    One more reason could be with the VHD incase if it was created from a running VM.

    Unfortunately, the only resolution you have for this scenario is to rebuild the VM. Please refer this document.

    Reference of common error codes of VM: https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/error-messages

    Hope this helps.
    Please 'Accept as answer' if the provided information is helpful, so that it can help others in the community looking for help on similar topics.

    Was this answer helpful?

Your answer

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