May 06 2020 09:23 AM
May 06 2020 09:23 AM
I'm curious if there is a way to increase the default disk size or add additional disks for Lab VMs? Some of our software packages are quite large! I haven't seem mention of this in the documentation or in the UI. Does it have to be done via PowerShell/AzureCLI?
Thanks in Advance,
May 26 2020 01:53 PMSolution
@tdickieson - One thing that I want to point out is that there is a general paradigm shift when you switch from a physical lab to using Azure Lab Services. A key difference is that Azure Lab Services is designed to spin up and tear down labs quickly as your needs change - typically, we recommend that you have 1 lab per class so that you only need to install the software for that one particular class and then when the class is over, you tear it down again. This is different compared to a physical lab that is shared by multiple classes and that requires all classes' software be installed at the same time. In most cases, if you create 1 lab per class, this typically reduces the amount of software that must be installed at one time within the lab and then reduces disk size needs. However, there are sometimes exceptions that a particular piece of software requires a larger disk size - if you have this situation, let us know.
Nov 05 2020 01:41 PM
Nov 05 2020 02:40 PM
@AndrewStrahl - Sure, this info helps me to understand your scenario. Although the current disk size is 128 GB, we did recently write a blog post that provides tips to help with nested virtualization. Here's a link to this post: https://techcommunity.microsoft.com/t5/azure-lab-services/nested-virtualization-tips/ba-p/1534323. In particular, refer to the guidance provided in bullet #2 in this post.
Nov 05 2020 02:57 PM
Nov 05 2020 04:49 PM
@AndrewStrahl currently the only other options I can think of would be to store the snapshots externally from the VM. Or, the other thought is to create multiple labs for the class so that the students use a different lab\VM depending on the set of assignments that they are working on. I realize that neither of these are ideal, but may be ways to work around this in the short term.
We have received this feedback before that for nested virtualization, a larger disk size than 128 GB would be useful. I'll make sure your feedback is tracked on our backlog to consider for the future.
Nov 05 2020 05:01 PM
Nov 05 2020 05:10 PM
@AndrewStrahl glad to hear that Az Labs is helping out. If your school needs any assistance with setting up labs based on the various needs of your classes, please let us know. We can potentially engage with your school\IT department directly to help implement this.
Also, we really appreciate your feedback. I would be interested to know what option you decide to go with to work around the 128 GB size limitation. And, we're always interested to learn more about the types of classes\scenarios that schools are using Az Labs for.
Feb 17 2021 03:04 PM
@tdickieson I have the same problem, I am trying to build a Hyper-V lab of VMs on the large instances (8 cores, 32GB RAM, nested virt) but 128GB of space is extremely limiting. I could find solutions for most of my other problems (how to transfer ISO files efficiently with a network share inside the same virtual network, for instance) but the disk size is definitely going to be a difficult problem to work with. I wish I could just pay more for a larger disk.
Feb 25 2021 06:27 PM
Mar 14 2021 12:55 PM
Mar 14 2021 07:01 PM