Azure Nested Virtualization with VMWare Workstation

preview_player
Показать описание
Update:
-D series doesn't seem to work
-Second reboot may not be needed (after the disable command).
-May need to perform the commands again if the Hyper-V error comes back randomly.

Azure environment tested:
Windows 10 2004
Standard E4s_v4
VMWare Workstation 16

PowerShell Commands:
Reboot
bcdedit /deletevalue hypervisorlaunchtype
bcdedit /set hypervisorlaunchtype off

Рекомендации по теме
Комментарии
Автор

Hi All,

It worked for me after trying various sizes and OS

what I used is mentioned below

VM SIZE - E4sV4, post installation I changed it to E8sV4 as extra compute was required for my test lab

OS - windows10 enterprise 21h2

Security Type of VM should be standard to enable nested virtualization (Trusted Virtual machine will not work)

sandeepchansauliya
Автор

Hello, I confirm that this solution works with specific versions, I tried with several and this is the only one that worked for me

Standard E4s v4 (4 vcpu, 32 GiB memory)

Windows (Windows 10 Enterprise) v1 22H2 enterprise

In my case I don't need a second reboot

Arvyy
Автор

Chris you are a good man buddy, I dont care what they say about you - 😂😂

logicfirst
Автор

Great video, going to try this out today!

WhyDoIPosttt
Автор

Great vid. Thanks. Quick question, did you have to do NAT or does bridging work? Not a big deal for workstations, but we have some old Linux VM's that won't run in Azure, so we are trying nested virtualizations, but the network seems to be the tricky part.

jasonredwine
Автор

thanks! i have tried lots of windows version and different service plans. At last i make it work! Specs : windows 10 pro 21h2 and Standard E4s v4 - Gen1. Also note that i didnt reboot after 2nd script, dunno if it matters

nitrogenius
Автор

Transport (VMDB) error -14: Pipe connection has been broken.?

usamasaleem
Автор

Sir i used windows server 2016 azure(GEN2), didnt work, , windows server 2019(GEN@), also didnt work, i used hyper V, the internet connection too didnt work..

danastudebaker
Автор

Windows 2016 don't have. When press right click is don't have program windows power sell. So I can't access to folder

nmhchannel
Автор

@Chris, were you able to find any solution to it as Windows 10 2004 is not available in Azure, please provide some workaround with the latest versions. Thanks in advance🙏

Pantzarixzon
Автор

That works perfect with NAT. Did anyone had a chance to make bridging work?

Deplated
Автор

Hey @Arvyy..I was trying to download the Zip file but it says the file is no longer available. How did u download that.

AnkitRaina-nc
Автор

Hello grate video but dir me it is not working with v4 windows 10 enterprise imagr ;( still the same error and next error after closing first is Transport (VMDB) error -14 pipe connection has been brokrn ;(

jonpok
Автор

I tried that with linux kali I wonder if it possible to install Mac also

oussamakifo
Автор

I will test now!


Edit: Just got this error after done everything on video "VMware Workstation and Device/Credential Guard are not compatible" any ideas for how to fix that?

luck
Автор

Hello, I tied with these sizes: Standard_E8as_v4 and Standard_E8s_v3 and it does not work

jovis
Автор

@Chris Martel Hi can you help with where you found the Windows 10 2004 Enterprise Gen1? Because I don't seem to find it or alternatively which other OS can work with this?

wincywilli
Автор

Tried this and the HyperV error isn't there but now I'm getting an error saying Device Guard / Credential Guard needs to be disabled.

NabilJain
Автор

Sir my vm inside that vmware is not loading it is giving black screen any suggestion

surajsalvi
Автор

I have diligently experimented with various Azure server types, investing 4 hours of my time. Regrettably, I must inform you that this method is no longer effective.

pkaycr