VM Not starting: agent status is not ready

Yoav 20 Reputation points
2023-02-24T18:18:41.9166667+00:00

Hello,

I stopped my VM in order to increase the size of my disk. When I try to start it again, it loads for 30 mins saying "Starting Virtual Machine". It sometimes says that it has started successfully. But it does not actually work, saying that the VM agent status is not ready.

Please advise on what I can do to resolve this issue.

Thank you.

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
9,014 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. JimmySalian-2011 42,486 Reputation points
    2023-02-24T18:35:19.4633333+00:00

    Hi,

    Seems like a corruption or some sort of loop , can you run this command to check the status of the agent Get-AzVM -ResourceGroupName $RGName -Name $vmName -Status

    Alco check this troubleshooting steps related to the VM agent - https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows-azure-guest-agent

    Hope this helps.

    JS

    ==

    Please accept as answer and do a Thumbs-up to upvote this response if you are satisfied with the community help. Your upvote will be beneficial for the community users facing similar issues.

    0 comments No comments

  2. vipullag-MSFT 26,487 Reputation points Moderator
    2023-02-27T03:13:30.4566667+00:00

    Hello Yoav

    Welcome to Microsoft Q&A Platform, thanks for posting your query here.

    Adding to previous response from Marshaljs, "VM agent status is not ready" error message indicates that there is an issue with the Azure VM Agent.

    You can try below troubleshooting steps:

    • Try to Restart the VM and see if that helps. In some cases, restarting the VM may help to resolve the issue.
    • You can try reinstalling the VM Agent. To do this, you can use the Azure PowerShell or Azure CLI command-line tools to execute the following command:
      Get-AzVM -ResourceGroupName <ResourceGroupName> -Name <VMName> | Remove-AzVM -Force This will remove the VM but keep the disks and network interfaces. After that, execute the following command to create a new VM with the same configuration: New-AzVM -ResourceGroupName <ResourceGroupName> -Location <Location> -Name <VMName> -ImageName <ImageName> -Size <VMSize> -OsDiskName <OSDiskName> -ManagedDiskId <ManagedDiskId> -OSDiskCaching <OSDiskCaching>
    • You can also check the VM Agent logs to identify any issues. To do this, you can connect to the VM using Remote Desktop or SSH and check the log files located in the following directory: C:\WindowsAzure\Logs\WaAppAgent.log If you are unable to resolve the issue using the above steps, try creating a new VM and attaching the existing disk to it. This will create a new VM with the same configuration but with a fresh VM Agent installation. Hope this helps. If you need further help on this, tag me in a comment. If the suggested response helped you resolve your issue, please 'Accept as answer', so that it can help others in the community looking for help on similar topics.

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.