Created a D4s VM Windows 10, virtualization in BIOS is not enabled.

Manju 110 Reputation points
2023-03-29T23:44:48.4533333+00:00

Since 2-3 days, any VMs (D3s / D4s, Windows 10) created don't have virtualization enabled. I had created a D2s VM about 2 months ago, that has virtualisation enabled.

Did anything change in Azure that is causing virtualization being not enabled ?

Thanks.

Manju

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
8,130 questions
0 comments No comments
{count} votes

Accepted answer
  1. TP 100.2K Reputation points
    2023-04-04T19:45:31.2266667+00:00

    Hi Manju,

    Please confirm that you created the Virtual Machine with Security type: Standard. If not, you will need to recreate your VM and choose Standard in order to use Nested Virtualization.

    azure security type standard

    Please click Accept Answer if the above was useful.

    Thanks.

    -TP

    4 people found this answer helpful.

2 additional answers

Sort by: Most helpful
  1. Sedat SALMAN 14,140 Reputation points MVP
    2023-03-29T23:53:50.8833333+00:00

    t is recommended to check the BIOS settings of the host machine to ensure that virtualization is enabled. Without virtualization enabled, nested virtualization will not work properly in Azure VMs. You can also check the host machine's firmware settings to make sure that they support nested virtualization. If nested virtualization is not supported, it is not possible to enable virtualization on VMs. Additionally, you can try creating a new VM and check if virtualization is enabled by default. If the issue persists, it is recommended to contact Azure support for further assistance.

    0 comments No comments

  2. Prrudram-MSFT 26,686 Reputation points
    2023-03-31T07:59:53.2366667+00:00

    Hi @Manju
    Thank you for reaching out to the Microsoft Q&A platform.

    The supported SKUs for nested virtualization are Dv3 and Dsv3-series and Dv4 and Dsv4-series

    The Hyper-V role needs to be enabled as soon as you create the VM with one of the above SKUs. This is also documented here https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/troubleshoot-vm-by-use-nested-virtualization#step-1-create-a-rescue-vm-and-install-hyper-v-role

    and here as well https://learn.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/nested-virtualization(Applicable for azure too)

    Blog post for reference: https://azure.microsoft.com/en-us/blog/nested-virtualization-in-azure/

    Hope this helps! :)

    Please feel free to tag me in your comments if you need additional help. Please accept as answer and upvote if the above information is helpful for the benefit of the community.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.