We’re excited to introduce the replacement of OS Images, the new VM Image object, with our most recent Microsoft Azure Runtime release. Sure, this may sound familiar to a few of you. This functionality was one of several interesting new features showcased at the /build conference in San Francisco a little over a week ago. The technical team have been more brutal at work to get this new entity out there, and I’m excited to start a series of postings outlining what it is, how to use it, and all the other minor, practical aspects. VM Images may be thought of as a more comprehensive image for Microsoft Azure Virtual Machines in a single statement.
It functions similarly to a disc today in that it is “ready to use,” but unlike a disc, the VHDs of a VM Image are viewed as read-only and replicated when a new virtual machine is deployed. A customised VM Image is intended to be used as a “snapshot” to deploy a virtual machine to a known point in time, such as checkpointing a development system, before executing an operation that may go wrong and leaving the virtual machine unusable. Due to the Windows need of Sysprep for image replication, it is not intended to be a means for cloning numerous identical virtual machines in the same virtual network.
Procedure to Use VM image
1. Using current or new Azure and Azure Stack setups, create bespoke Linux and Windows images at scale.
2. Create an image build pipeline and global management system by integrating Azure DevOps with Shared Image Gallery.
3. Connect VM Image Builder to your current virtual networks to leverage your configuration servers and resources.
4. Use your current scripts, commands, and procedures to migrate an image customisation pipeline to Azure.
How Can you Create VM Image ?
You may capture a virtual machine’s instance as a VM Image once it’s set up and configured to your liking. All essential attributes of the virtual machine and discs are saved throughout the capture process and copies of the backup VHD page blob(s). Each VHD duplicate is kept in the same storage account and container as the original VHD.
The virtual machine will be removed automatically once recorded as a VM Image. The virtual machine can be captured while running or shut off if the operating system is tailored. We recommend shutting down the virtual machine before capturing the VM Image if an application consistent or cross-disk capture is required.
How Can you Use VM Image ?
When building a virtual machine as part of a new or existing deployment, you can utilise a VM Image. To create a new virtual machine, first, ensure that the virtual machine and VM Image locations are identical, and then specify the name of the VM Image to use.
Provisioning information and network setup should be included in the VM Image are universal, just as they are with an OS Image today. Once deployed, the virtual machine functions similarly to any other VM generated from OS Images or OS discs. The role may be modified, new discs can be added, or current discs removed.
However, the virtual machine may still be loading up, necessitating a few more minutes for remote desktop/SSH to be available. After the virtual machine has been deployed and started, it functions similarly to any other VM generated from OS Images or OS discs. When you deploy new virtual machines from a customised Windows VM Image collected from a running VM, there is one little caveat to this statement.
When you first remote desktop into a newly deployed VM utilising such a VM Image, a dialogue box may appear claiming that the VM was not properly terminated.
Eliminate the headaches of working out tooling, procedures, and unnecessary manual steps. Create unique images using Azure VM Image Builder in a few easy steps. Connect to Shared Image Gallery to integrate the image creation process with your existing DevOps pipeline and manage the photos.
Get Your Free Consultation regarding Azure VM image if you need further assistance.