Forum Discussion
VM Disk Size
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.
MicrosoftAndrewStrahl - 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.
Thanks,
Nicole
- I think the default is to thin provision the disks (using vhdx).
For us it's not the size of the disk that is cuaing issues, just the ability to take multiple snapshots of each VM.
For example, if we have 6 VMs, and ten assignments for the class, they would need nine snapshots if they want to go back and practice.- nicolehaugen
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.
- We thought of attaching a storage share in the VNet for students to store snapshots. This is fairly new for us (just learned of lab services two weeks ago) so we are still figuring out what works and what won't.
We won't give up, I'm sure we can find something that will work.
Gotta admit though, this is such a game changer for us during covid!
