Introduction
When you have an on-premises Virtual Machine and if you need to move it to the cloud, you should create a Virtual Hard Disk. The virtual hard disks are of two types - VHD and VHDX. Unfortunately, the Microsoft Azure cloud supports only the generation 1 VMs which are VHD. These VHDs are fixed size and the maximum size allowed is 1023 GB. Here, in this article, we are going to see how we can spin up a Virtual Machine in Azure from the VHD file we have. I will explain why I came to this situation in the "Background" section. I hope you will find this article useful. You can always read this article on my blog here.
Background
I was working with a product called UCS (University Corporate Server). You can consider it as a private Play Store where you can install and use your custom applications. Also, you are allowed to use the existing ones as well. Now, I wanted to create an Azure VM with the UCS in it, but all I had in my hand was a VHDX file that is not supported in Azure.
Steps
In this article, we will be doing the following tasks.
- Converting the VHDX file to VHD
- Uploading it to the Azure Blob storage
- Creating a Managed Image from the VHD
- Creating the Virtual Machine from the Managed Image
Spin up the Azure VM from VHDX
As we have discussed, the first step is to convert the VHDX file to VHD.
Convert VHDX to VHD
We are going to use PowerShell for the conversion as it has some modules already to support this conversion.
Convert-VHD –Path c:\CreateVM\ucs.vhdx –DestinationPath c:\CreateVM\ucs.vhd -VHDType Fixed
Please note that the Argument -VHDType is very important, otherwise, you may be getting an error as follows, when you try to create the Managed image using the command New-AzImage.
- New-AzImage: Only blobs formatted as VHDs can be imported.
- ErrorCode: InvalidParameter
- ErrorMessage: Only blobs formatted as VHDs can be imported.
- ErrorTarget: disks
- StatusCode: 400
- ReasonPhrase: Bad Request
- OperationID: 16baa116-be93-4054-8ba9-265eda636f0c At line:1 char:10 + $image = New-AzImage -ImageName $imageName -ResourceGroupName $rgName ... + ~~~~~ + CategoryInfo : CloseError: (:) [New-AzImage], ComputeCloudException + FullyQualifiedErrorId : Microsoft.Azure.Commands.Compute.Automation.NewAzureRmImage
Once you are done a new VHD image will be created in the destination path you have given. Please note that the size of this file may be huge, and when you upload it to the Blob storage, it may take longer depending on the network speed you have.
Upload the VHD file to Azure blob storage
As a prerequisite, you should create a storage account before you start this process. Once you have created the storage account, you are good to go and start the upload. Go to your Storage account, and click on the Blobs under blob services.
Now you can click on the +Container menu item and create a new container which is nothing but the container for your files. Now we can go inside the container and click on the Upload button. In the upcoming pop up you can select the VHD file using the file picker option and upload the file. As I said earlier, this process depends on your network speed.
Sometimes, due to the browser's inactivity, uploading heavy files to the blobs using the Azure portal can be a headache as it throws an error. One of the suggestions I can give you here is to use the Azure Storage Explorer tool, which is quite easy to use and effective. Once you download the tool, log in with your Azure credentials, go to the storage accounts, and click on Blob Containers. In the new window click on Upload and then Upload files.
Please make sure that you are selecting the Blob type as Page Blob and then click Upload. The uploading is faster if you are using the tool instead of the portal.
Create a Managed Image from the VHD file
As we have our VHD file in our Blobs, now it is time to create an Image from the file. We are going to write some PowerShell commands to do the work for us. To set the configuration we are going to use the command New-AzImageConfig. If you are getting the error “The term New-AzImageConfig ‘ is not recognized as the name of a cmdlet”, you should install and import the module Az. Compute.
Install-Module Az.
Compute import-module Az.
Compute
It is possible to get some additional error when you try to install the Az. Compute module. In that case, you can try the preceding command.
Install-Module Az.
Compute -AllowClobber
Once that is done, we can set some variables in the PowerShell as follows.
$vmName = "ucs"
$rgName = "ucs"
$location = "West Europe"
$imageName = "ucs"
$osVhdUri = "https://ucs.blob.core.windows.net/files/ucs.vhd"
Now we can start the image creation as preceding.
$imageConfig = New-AzImageConfig -Location $location
$imageConfig = Set-AzImageOsDisk -Image $imageConfig -OsType Linux -OsState Generalized -BlobUri $osVhdUri
$image = New-AzImage -ImageName $imageName -ResourceGroupName $rgName -Image $imageConfig
As the UCS is a Linux-based system, I had given the -OsType as Linux, you may have to change it as per your needs. If you try to run the command New-AzImage with the VHDX blob, you will get an error as below.
- New-AzImage: Blob name in URL https://ucs.blob.core.windows.net/files/ucs.vhdx must end with ".vhd" extension.
- ErrorCode: InvalidParameter
- ErrorMessage: Blob name in URL https://ucs.blob.core.windows.net/files/ucs.vhdx must end with ".vhd" extension.
- ErrorTarget: blobUri
- StatusCode: 400
- ReasonPhrase: Bad Request
- OperationID: 668b8e66-85b3-4c7b-a182-4f155e16b66d At line:1 char:10 + $image = New-AzImage -ImageName $imageName -ResourceGroupName $rgName ... + ~~~~~~~ + CategoryInfo : CloseError: (:) [New-AzImage], ComputeCloudException + FullyQualifiedErrorId : Microsoft.Azure.Commands.Compute.Automation.NewAzureRmImage
But we don’t need to worry about it as we have already converted our VHDX file to VHD format. Once the New-AzImage command is successful, you can see the image in the Azure portal if you go to the Images section. You can search for the keyword “Images” in the portal.
Create a VM from the Managed image
As we have the image now, we can create our VM easily from the Azure portal. Go to the Images select your image and then click on the button Create VM. On the next page, you can give the details of your VM. You can also create the VM by using the PowerShell command as preceding.
New-AzVm ` -ResourceGroupName "myResourceGroup" ` -Name "myVMfromImage" ` -ImageName "myImage" ` -Location "East US" ` -VirtualNetworkName "myImageVnet" ` -SubnetName "myImageSubnet" ` -SecurityGroupName "myImageNSG" ` -PublicIpAddressName "myImagePIP" ` -OpenPorts 3389
Once you have filled in all the details, you can either click on the Review+Create or you can go through each step. The creation of a VM can take a few minutes. Once the task is done, you can go to your Virtual Machine and spin up the same. I would also recommend you assign a static IP and DNS name to your VM.
Conclusion
In this article, we have learned
- What are VHDX and VHD files
- How to convert the VHDX file to VHD
- How to upload VHD files to Azure Blob storage
- How to create a Managed Image from the VHD file in Azure
- How to create a Virtual Machine using the Managed Image
Your turn. What do you think?
Thanks a lot for reading. Did I miss anything that you may think is needed in this article? Did you find this post useful? Kindly do not forget to share your feedback.
PrakashPosted Jun 18, 2019, 3:34 PM
Sibeesh, This article is good and very useful.. I followed this create a VM from the VHDX source. But I got stuck at VM creation I used the command " New-AzVm -ResourceGroupName $RGName -Name "AzureVM" -ImageName $ImageName -VirtualNetworkName "VNET-xxxx" `-SubnetName "Subnet-1" -SecurityGroupName "NSG" -Location $Location -Size "Standard A4 v2" " getting error New-AzVm : Resource 'AzureVM' was disallowed by policy. Please advise