Debian VHD uploaded to Azure shows Windows licenses under Create VM

Lian Sabella Castillo 0 Reputation points
2023-12-26T08:04:53.9133333+00:00

I uploaded a VHD file through storage explorer explicitly choosing Linux under OS dropdown. I have uploaded other Linux VHDs and they were able to boot fine. This time it only shows Windows Client/Windows Server over the usual Red Hat options.

When I do try to continue with a Windows client, it says "OS conflict"

Is there a way to override this?

Azure Storage Explorer
Azure Storage Explorer
An Azure tool that is used to manage cloud storage resources on Windows, macOS, and Linux.
240 questions
Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,871 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sumarigo-MSFT 44,906 Reputation points Microsoft Employee
    2023-12-27T06:28:14.17+00:00

    @Lili Cas Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

    Can you please share the screenshot of the error message?

    If you uploaded a VHD file through Storage Explorer and explicitly chose Linux under the OS dropdown, but it is showing Windows Client/Windows Server options instead of the usual Red Hat options, it is possible that the VHD file was not uploaded correctly or that it is not a valid Linux VHD file.

    Unfortunately, there is no way to override the OS conflict error message. The OS conflict error message indicates that the VHD file has metadata that conflicts with the OS type that you selected in Storage Explorer.

    Here are some things you can check to troubleshoot the issue:

    • Check if the VHD file was uploaded correctly. Make sure that the VHD file was uploaded correctly and that there were no errors during the upload process.
    • Check if the VHD file is a valid Linux VHD file. Make sure that the VHD file is a valid Linux VHD file and that it is not corrupted or damaged.
    • Check if the VHD file has the correct metadata. Make sure that the VHD file has the correct metadata, including the OS type and version.
    • Try uploading the VHD file again. Sometimes, uploading the VHD file again can help resolve the issue.
    • Ensure that you have the correct permissions to upload the .vhd file to Azure. You'll need to have the appropriate role-based access control (RBAC) permissions to upload the file.
    • Check the size of the .vhd file. Azure has a maximum size limit of 2 TB for .vhd files. If your file is larger than this, you'll need to split it into multiple .vhd files.
    • Ensure that the .vhd file is not corrupted. You can use the 'chkdsk' command in Windows to check the file system for errors.
    • Ensure that the .vhd file is in the correct format. Azure supports both .vhd and .vhdx formats, but the file must be in the fixed format, not dynamic. If you've checked all of these items and are still encountering an error, you can try uploading the .vhd file using the Azure CLI or Azure PowerShell. These tools provide more detailed error messages that can help you troubleshoot the issue.

    Additional information:

    Reference:

    Please let us know if you have any further queries. I’m happy to assist you further.

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.