An VM stuck in "creating"
Hello, After the outage issue this morning, one of the VMs in our labs has been stuck all day in the "Creating..." state. There is nothing I can do to affect it It is okay to delete that particular VM or reimage, but those options do not work for me. Any information would be appreciated.
Cannot start VMs, template, or create a new lab
We are currently seeing an issue where we cannot start our VMs, we just see this message: "Virtual machine redeploy operation failed. Try redeploying the virtual machine. If the issue persists, consider reimaging it. For further assistance submit a support request." Redeploying does not make any difference, and we are reluctant to reimage as MS have acknowledged a bug whereby the SSD of the VM can shrink after a reimage: in any case we also cannot start our template. We cannot make a new lab: when we try we see the "gorilla holding a sign" indication that something has gone wrong on both the dashboard and template pages for that lab. Our lab plan is based in UK South. We are unable to create an alternative lab plan in another region as the portal says we are not allowed to due the retirement of ALS in 2027! Has anybody seen similar and has any suggestions?I cannot set the lab capacity when publishing the template.
Hello, A lab has been created before, and its capacity is zero currently. When I publish the lab, there is no option to set the virtual machine capacity, so there is no VM. When I send the invitation link to a user, it says all VMs are claimed.... . Can someone help me with this issue? Thanks.
AZURE LAB USER SQL DB DELETE EACH TIME I REPUBLISH
@community Good morning Community members, I am having an issue, each time I republish the VM from the labs.azure.com portal the following happens: the entire document and wipe off the numerous installed app memory restarts ( e.g the extensions in VS code need to be reinstall) the databases created by the users also clear off Please, can you help me with a step-by-step guide to prevent this from happening? I appreciate your help, dear community members.LAB VM Hardening loosing connectivity
Hi, I need some help here, I am working on a project on an AzureLab to automate the installation of a Privileged Access Management solution (CyberArk). The problem I am encountering is that the Vault VM (containing passwords) needs a drastic hardening. Everything works until I restart the VM after the hardening process from AzureLAB (I am able to restart it from windows without a problem). The starting button never ends and after 10 minutes the VM is disconected. However, until those 10 minutes I am still able to use it as if it worked completly fine. My only clue here is I suppose that AzureLAB uses behind the scenes a specific utility to check if the VM is actually started, wich is blocked by my hardening ? Does anyone already encountered a similar problem ? Any help would be appreciated, thanks.
Unplanned Outage?
Hi Lab Services team, Are there any updates I can share with my affected users? Students have assignments due tomorrow (Monday 13/05, Australia East) and I'm having to tell the subject coordinators that they won't be able to hand them in. What are your current theories about the cause or estimates for a timeline?Disk throughput performance differences between template and pool VM
Hi, While testing a Lab I'm preparing, I noticed that the disk throughput performance of my template was as much as 5 times faster compared to a pooled VM from that very same template. I'm using the "Large VM (nested virtualization)" template with the "128 GB Premium SSD" option. The template itself reaches about 150 Mbyte/s, while the pool VM maxed out at 30 MByte/s. The VM is running Ubuntu 22.04 LTS. I'm testing as follows: dd if=somebigVMfile.vdi of=/dev/null bs=1M status=progress Is there something wrong with the pool VM? Anything it can/should/must do to change this? 30 Mbyte/s is way too slow for a "premium SSD". Thank you!
Azure Lab Services - Planned Outage - April 19, 2024
Hello Everyone, On April 19th, 2024, we will be updating our system between 1:00-10:00 pm UTC. Please expect downtime for most common operations like create/ update/ delete labs, start/stop virtual machines etc. The service will be available after the update. We will provide update on this post once the service update is complete. Thank you for your patience. - Lab Services team.Labs Backup and restore (whole lab)
Hi community! I hope you can give me a hand. We just started working with Azure lab services and we love the tool; but I haven't found a way to backup a lab, how could I do it? That is, if someone accidentally deletes a lab, is it possible to have a backup of that lab to restore it? I mean, not of the Virtual Machines, but a backup of the whole lab; or, at least, a backup of the customized and published imaged used to deploy the Virtual Machines I would appreciate if you share any idea of how to do it; I have not found anything about this in the official documentation. Thank you very much in advance!