ProvisioningState/failed/OSProvisioningTimedOut error when booting up the VM

Quaseem 21 Reputation points
2020-07-22T16:42:50.3+00:00

Hi Team,

When I am trying to power on my virtual machine from Azure portal. Its taking a lot of time but eventually VM is booting up and below error generating in the portal. Any help will be highly appreciated.

GENERAL
Provisioning state Provisioning failed. OS provisioning failure has reached terminal state and is non-recoverable for VM 'VM name'. Consider deleting and recreating this virtual machine. Additional Details: { "resourceType": "Microsoft.WindowsAzure.ComputeResourceProvider.Core.Shared.Strings, CRP.Core.Shared, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null", "ResourceCode": "OSProvisioningTimedOut", "ResourceParameters": [ "VM name" ] }. OSProvisioningTimedOut

Provisioning state error code,
ProvisioningState/failed/OSProvisioningTimedOut

Guest agent,
Ready. GuestAgent is running and processing the extensions.

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,579 questions
{count} votes

Accepted answer
  1. vipullag-MSFT 26,016 Reputation points
    2020-07-23T05:38:01.147+00:00

    @Quaseem

    As you mentioned that you are seeing this error when you are trying to power-on VM from Azure portal, based on this looks like the VM is in deallocated state and you are starting it. Also, the VM is booting up with error (Is the VM working as expected thought it is taking more time to boot?) Assuming it is working but you are seeing the error on Azure portal.

    This could mostly be due VM sync issues with the host.

    Below are few suggestions to try and see if they help resolve the issue:

    Change VM Size:
    Try to Change the Size/Family of the VM from existing size to a new size, this will move the VM to a new host. And later you can try to come back to the original VM size.

    • Stop the VM.
    • Select the VM size and then pick a new size and click on Resize.
    • Start the VM.

    Redeploy VM:

    • In the Azure Portal, head over to the problematic VM.
    • Go to the bottom of the VM’s settings blade and click on, redeploy to start the process of redeploying the VM to a new node.
    • It shouldn’t take no more than 15 minutes to redeploy the VM.
    • Once completed, check if you are still seeing any errors on the portal.

    Reference document.

    Recreate VM:
    Create a Snapshot of the OS Disk in Azure of the VM:

    • Go to the VM and head over to the Disks blade.
    • In the disk blade and select the OSDisk.
    • In the OS Disk's menu, select create snapshot.
    • In the snapshot window in Azure, name the snapshot and select the corresponding resource group.
    • Click create and wait for a couple minutes.
    • Once the snapshot is created, go to create resources tab.

    You can use this script to create a VM from the os disk snapshot.

    Also, please refer these documents for VM common errors for more information.

    Understand common error messages when you manage virtual machines in Azure.

    Troubleshoot deployment issues when creating a new Windows VM in Azure.

    Linking similar issue for reference.

    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.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful