Azure Lab Services some VM's stuck at starting

Question

Azure Lab Services some VM's stuck at starting

C O'Connell 0

I am running Lab Services VM's for our students and all has been well for a number of months. But now I have 3 VM's stuck at the starting phase.

I cannot redeploy them as these options are removed when the VM is starting phase.

Any suggestions on how to get things working again?

1 answer

Your answer

Answer 1

Anonymous

Hi C O'Connell,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

To help investigate the issue of VMs stuck in the "Starting" phase, we need a bit more information:

Are schedules set for the lab? If yes, what are the start and stop times?
Have there been recent updates, such as image changes, VM size adjustments, or configuration updates?
Are other VMs in the lab starting correctly, or is the issue limited to these three VMs?
Have you tried restarting the lab, individual VMs, or force-stopping them using PowerShell or CLI?

Please refer to below documentation:
https://techcommunity.microsoft.com/blog/azurelabservicesblog/hardware-support-change-with-gpu-labs-that-use-lab-accounts/4020895
https://learn.microsoft.com/en-us/azure/lab-services/troubleshoot-connect-lab-vm

Anonymous

2024-12-11T01:39:40.72+00:00

Hi C O'Connell,

Just following up to see if you had a chance to review my earlier questions. The additional details will help us investigate and provide a more accurate resolution for the issue with the VMs stuck in the "Starting" phase.

Looking forward to your response.

Thank you.
C O'Connell 0 Reputation points

2024-12-11T09:20:00.7533333+00:00
Are schedules set for the lab? If yes, what are the start and stop times? No Schedules set

Have there been recent updates, such as image changes, VM size adjustments, or configuration updates? No Changes to anything

Are other VMs in the lab starting correctly, or is the issue limited to these three VMs? It started with one VM but now approx 10 are stuck starting and 10 are stuck stopping.

Have you tried restarting the lab, individual VMs, Yes or force-stopping them using PowerShell or CLI? No not yet is there detailed instructions on this?

The labs that are stuck in the stopping phase are being charged for.

The labs have been running for a few months with no issues. We have been running Lab Services for a number of years again with no issues.
Anonymous

2024-12-11T21:20:19.73+00:00
Hi C O'Connell,

Thank you for the update. Based on the information provided, here are some steps you can try to resolve the issue.

You can use Azure CLI to force-stop and restart the VMs.

# Stop the VM forcefully az vm stop --resource-group <ResourceGroupName> --name <VMName> # Start the VM az vm start --resource-group <ResourceGroupName> --name <VMName>

If multiple VMs are affected, you can restart the entire lab from the Azure portal. Navigate to the lab in the Azure portal and select Restart Lab under the Operations section.

Since VMs stuck in the "Stopping" phase are still being charged, it's essential to resolve this quickly. If force-stopping or restarting the VMs doesn’t work, I recommend opening an Azure Support ticket to investigate further and ensure billing adjustments if needed.

Additionally, check the Azure Service Health dashboard for any ongoing issues in your region that might be affecting Lab Services.

If you have any further queries, do let us know. If the comment is helpful, please click and "Upvote".
C O'Connell 0 Reputation points

2024-12-12T10:47:02.9+00:00

Hi

I Tried to use Stop-AzLabServicesUserVM -ResourceGroupName "Group Name" -LabName "Lab Name" -Email "******@contoso.com"

But I am getting this error

Stop-AzLabServicesUserVM_Stop: The term 'Az.LabServices.private\Get-AzLabServicesUserVM_Get' is not recognized as a name of a cmdlet, function, script file, or executable program.

Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

I have Install-Module -Name Az -Repository PSGallery -Force and Install-Module -Name Az.LabServices -RequiredVersion 0.1.0 installed to Azure Powershell.

But I have been informed by a new support ticket that VM'S are hosted in a subscription managed by the product team and the customer does not have powershell access. I am the Owner/Admin of the Lab Services VM's
Anonymous

2024-12-12T22:37:02.3533333+00:00
Hi C O'Connell,

Thank you for the update. Based on your reply, it seems the issue may be related to the Az.LabServices module version or subscription restrictions.

Update the Module: The version 0.1.0 is a pre-release. Try updating to the latest version:

Update-Module -Name Az.LabServices

Restart PowerShell after updating.

Use the Azure Portal: Since PowerShell access is restricted, manage the stuck VMs through the Azure portal. Navigate to the lab, select the VMs, and attempt to stop or restart them from there.

Verify Permissions: If the subscription is managed by the product team, you may need their assistance for actions like force-stopping VMs.

For more details, please refer to the below documentation:
Azure role-based access control in Azure Lab Services

If you have any further queries, do let us know. If the comment is helpful, please click and "Upvote".

Share via

Azure Lab Services some VM's stuck at starting

1 answer

Your answer