%3CLINGO-SUB%20id%3D%22lingo-sub-1455968%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1455968%22%20slang%3D%22en-US%22%3E%3CP%3EAwesome%20news!%20Hyper-V%20is%20my%20favorite%20Hypervisor%20and%20the%20most%20powerful%20one.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1456543%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1456543%22%20slang%3D%22en-US%22%3E%3CP%3EWhere%20do%20we%20go%20to%20find%2C%20or%20monitor%20progress%2C%20with%20Hyper-V%20Default%20vSwitch%20enhancements%20or%20fixes%3F%26nbsp%3B%20It's%20still%20causing%20many%20bandwidth%20issues%20with%20certain%20wifi%20choosers%2C%20so%20it%20seems.%20Our%20team%20needs%20a%20fix.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1456829%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1456829%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20a%20wonderful%20news.%20However%20%22%3CSPAN%3EUse%20a%20Windows%20guest%20with%20an%20OS%20version%20that%20is%20greater%20than%20or%20equal%20to%20the%20host%20OS%20version%20(19636)%20for%20now.%26nbsp%3B%3C%2FSPAN%3E%22%20is%20not%20a%20correct%20statement%20in%20my%20opinion.%20I%20was%20able%20to%20successfully%20use%20Windows%2010%201909%20in%20the%20guest%20which%20is%20the%20version%20of%20Windows%20far%20below%20the%2019636.%20From%20my%20own%20testing%20every%2064%20bit%20Windows%20operating%20system%20is%20working%20as%20a%20guest%20and%20it%20does%20not%20have%20to%20be%20newer%20than%2019636.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1457651%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1457651%22%20slang%3D%22en-US%22%3E%3CP%3EKind%20of%20way%20overdue%2C%20but%20thank%20you%20Microsoft%2C%20this%20is%20a%20great%20day%20for%20large%20(and%20fast%20growing)%20segment%20of%20your%20users.%20Looking%20forward%20to%20this%20landing%20in%20stable%20builds...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F696646%22%20target%3D%22_blank%22%3E%40proboszcz%3C%2FA%3E%26nbsp%3B%20-%20I%20am%20guessing%20that%20is%20the%20usual%20%22just%20in%20case%22%20to%20cover%20all%20bases%2C%20plus%20with%20all%20the%20work%20on%20mixed%20hypervisors%20and%20Linux%20community%2C%20that%20soon%20we%20will%20have%20support%20for%20all%20weird%20mixes%20like%20VMware%2C%20KVM%2C%20and%20any%20old%20weird%20OS%20we%20can%20think%20of.%20But%20thanks%20for%20confirming%20it%20that%20quickly!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1457912%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1457912%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F696646%22%20target%3D%22_blank%22%3E%40proboszcz%3C%2FA%3E%26nbsp%3BLpAdm%20is%20absolutely%20right.%26nbsp%3B%20We%20haven't%20validated%20the%20scenarios%20and%20performance%20on%20earlier%20versions%20of%20Windows.%26nbsp%3B%20In%20order%20to%20ensure%20a%20high%20performance%2C%20we%20have%20to%20have%20some%20enlightenments%20in%20the%20guest%20OSs.%26nbsp%3B%20This%20is%20also%20why%20we%20didn't%20bring%20up%20Linux%20support%20yet.%26nbsp%3B%20We're%20still%20working%20on%20some%20enlightenments%20there.%26nbsp%3B%20Once%20we%20have%20that%2C%20I'll%20make%20another%20post%20to%20share%20with%20the%20community%20at%20large.%26nbsp%3B%20Keep%20trying%20things%20out!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EChris%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1458086%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1458086%22%20slang%3D%22en-US%22%3E%3CP%3ENow%20please%20enable%20me%20to%20use%20nested%20virtualization%20in%20the%20root%20domain%20(in%20Windows).%20This%20is%20the%20last%20puzzle%20piece%20that%20keeps%20me%20from%20upgrading%20to%20WSL2.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1459425%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1459425%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F697013%22%20target%3D%22_blank%22%3E%40LpAdm%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F676358%22%20target%3D%22_blank%22%3E%40chuybregts%3C%2FA%3E%26nbsp%3B%2C%20I%20totally%20agree%20with%20you.%20However%20I%20think%20it%20would%20be%20better%20to%20change%20that%20statement%20to%20something%20like%20this%20%3A%20%22For%20maximum%20stability%20and%20performance%20u%3CSPAN%3Ese%20a%20Windows%20guest%20with%20an%20OS%20version%20that%20is%20greater%20than%20or%20equal%20to%20the%20host%20OS%20version%20(19636)%20for%20now%3C%2FSPAN%3E%22%20which%20will%20be%20more%20precise%2C%20because%20the%20current%20one%20suggests%20that%20using%20older%20versions%20of%20Windows%20will%20not%20work%20at%20all%2C%20which%20is%20not%20the%20case.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1459690%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1459690%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%20enable%20this%20also%20for%20older%20AMD%20Processors!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1434841%22%20slang%3D%22en-US%22%3EAMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1434841%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AMD%20nested%20MN_RELEASE%2019636.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F196082i53E2A2758A0F33FC%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22AMD%20nested%20MN_RELEASE%2019636.png%22%20alt%3D%22AMD%20Nested%20Support%20showing%20a%20VM%20running%20on%20a%20VM%20on%20AMD%20Hardware%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EAMD%20Nested%20Support%20showing%20a%20VM%20running%20on%20a%20VM%20on%20AMD%20Hardware%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fvirtualization%2Fhyper-v-on-windows%2Fuser-guide%2Fnested-virtualization%3Fredirectedfrom%3DMSDN%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ENested%20Virtualization%3C%2FA%3E%20is%20not%20a%20new%20idea.%20In%20fact%2C%20we%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fvirtualization%2Fwindows-insider-preview-nested-virtualization%2Fba-p%2F382256%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eannounced%3C%2FA%3E%20our%20first%20preview%20of%20Nested%20Virtualization%20running%20on%20Windows%20way%20back%20in%202015.%26nbsp%3B%20From%20that%20Windows%20Insider%20preview%20to%20now%2C%20Nested%20Virtualization%20has%20been%20used%20in%20a%20variety%20of%20offerings%20in%20a%20variety%20of%20ways.%26nbsp%3B%20Today%2C%20you%20can%20find%20Nested%20Virtualization%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-machines%2Fwindows%2Fnested-virtualization%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Esupport%3C%2FA%3E%20in%20Azure%20that%20gives%20the%20Azure%20users%20flexibility%20in%20how%20they%20want%20to%20setup%20their%20environments.%26nbsp%3B%20An%20example%20of%20Nested%20Virtualization%20being%20used%20to%20support%20our%20developer%20community%20is%20to%20accelerate%20Microsoft%E2%80%99s%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fxamarin%2Fandroid%2Fget-started%2Finstallation%2Fandroid-emulator%2Fhardware-acceleration%3Fpivots%3Dwindows%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAndroid%20Emulation%3C%2FA%3E.%26nbsp%3B%20Nested%20Virtualization%20is%20being%20used%20by%26nbsp%3B%20IT%20Pros%20to%20set%20up%20a%20home%20labs.%20And%20we%20can%E2%80%99t%20forget%20containers!%20If%20you%20want%20to%20use%20a%20Hyper-V%20Containers%20inside%20a%20VM%2C%20you%20guessed%20it%3A%20this%20is%20enabled%20with%20Nested%20Virtualization.%26nbsp%3B%20You%20can%20start%20to%20see%20why%20Nested%20Virtualization%20is%20such%20a%20useful%20technology.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20is%20one%20group%20of%20users%20that%20was%20unable%20to%20take%20advantage%20of%20Nested%20Virtualization%20on%20Windows.%20These%20were%20our%20users%20with%20AMD%20hardware.%26nbsp%3B%20Not%20a%20week%20goes%20by%20where%20the%20team%20doesn%E2%80%99t%20get%20a%20request%20for%20Nested%20Virtualization%20support%20for%20AMD%20from%20our%20community%20or%20from%20within%20Microsoft.%26nbsp%3B%20In%20fact%2C%20it%20is%20the%20number%201%20ask%20on%20Windows%20Server%E2%80%99s%20%3CA%20href%3D%22https%3A%2F%2Fwindowsserver.uservoice.com%2Fforums%2F295047-general-feedback%2Ffilters%2Ftop%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Euservoice%20page%3C%2FA%3E.%20At%20the%20time%20of%20this%20blog%20post%2C%20it%20was%20almost%205x%20more%20than%20the%20next%20feedback%20item.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20am%20happy%20to%20announce%20that%20the%20community%20has%20been%20heard%20and%20starting%20with%20Windows%20Build%2019636%2C%20you%20will%20be%20able%20to%20try%20out%20Nested%20Virtualization%20on%20AMD%20processors!%20If%20you%E2%80%99re%20on%20the%20Windows%20Insider%20Fast%20ring%20then%20you%20can%20try%20this%20out%20today.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20this%20is%20a%20preview%20release%20of%20Nested%20Virtualization%20on%20AMD%2C%20there%20are%20some%20guidance%20and%20limitations%20to%20keep%20in%20mind%20if%20you%20want%20to%20try%20this%20out.%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EEnsure%20your%20OS%20build%20number%20is%2019636%20or%20greater%3C%2FLI%3E%0A%3CLI%3ERight%20now%2C%20this%20has%20been%20tested%20on%20AMD%E2%80%99s%20first%20generation%20Ryzen%2FEpyc%20or%20newer%20processors%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EFor%20maximum%20stability%20and%20performance%20u%3C%2FSPAN%3E%3CSPAN%3Ese%20a%20Windows%20guest%20with%20an%20OS%20version%20that%20is%20greater%20than%20or%20equal%20to%20the%20host%20OS%20version%20(19636)%20for%20now%3C%2FSPAN%3E.%26nbsp%3B%20Linux%20KVM%20guest%20support%20will%20be%20coming%20in%20the%20future%3C%2FLI%3E%0A%3CLI%3ECreate%20a%20version%209.3%20VM.%20Here%E2%80%99s%20an%20example%20PowerShell%20command%20to%20ensure%20a%20version%209.3%20VM%20is%20being%20used%3A%20%26nbsp%3BNew-Vm%20-VMName%20%E2%80%9CL1%20Guest%E2%80%9D%20-Version%209.3%3C%2FLI%3E%0A%3CLI%3EFollow%20the%20rest%20of%20the%20steps%20in%20our%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fvirtualization%2Fhyper-v-on-windows%2Fuser-guide%2Fnested-virtualization%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Epublic%20documentation%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJune%2012%2C%202020%20edit%3A%20changed%20wording%20around%20Guest%20OS%20recommendation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1434841%22%20slang%3D%22en-US%22%3E%3CP%3EAnnouncing%20AMD%20Nested%20Virtualization%20support%20available%20through%20the%20Windows%20Insider%20Fast%20ring.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1471798%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1471798%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F676358%22%20target%3D%22_blank%22%3E%40chuybregts%3C%2FA%3E%26nbsp%3BCan%20you%20tell%20us%20if%20this%20feature%20is%20planned%20to%20be%20included%20in%20Windows%2010%2020H2%20final%20release%3F%20Also%20what%20about%20Windows%20Server%202019%20-%20is%20it%20planned%20to%20be%20included%20to%20it%20or%20have%20we%20wait%20till%20the%20next%20big%20Windows%20Server%202022%20version%3F%3C%2FP%3E%3CP%3EYou%20also%20told%20something%20about%20enlightenments%20that%20should%20be%20included%20in%20level1%20guest%20os%20for%20full%20performance.%20Will%20those%20enlightenments%20be%20propagated%20to%20earlier%20versions%20of%20Windows%20like%20Windows%2010%201909%2C%20Windows%20Server%202019%2C%20etc.%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20dedicated%20place%20where%20we%20can%20share%20our%20experience%20with%20this%20feature%20(report%20bugs%2C%20compatibility%2C%20etc)%20or%20should%20we%20do%20this%20here%20in%20the%20comments%20and%20Feedback%20Hub%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1472164%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1472164%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20adding%20nested%20virtualization%20for%20AMD!!%26nbsp%3B%20Now%20if%20I%20could%20only%20get%20my%20android%20emulator%20to%20work%20in%20nested%20mode...%20but%20that's%20another%20story.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EREFS%20heads%20up%3A%26nbsp%3B%20During%20the%20upgrade%20your%20writable%20REFS%20volumes%20will%20be%20upgraded%20to%20REFS%20version%203.5%20and%20will%20not%20be%20readable%20prior%20to%20any%20build%20before%2019536%20(which%20includes%202004%2F19041%20and%20earlier%20builds).%26nbsp%3B%20When%20reverting%20your%20build%2C%20you'll%20lose%20access%20to%20your%20REFS%20volumes.%26nbsp%3B%20REFS%20volume%20upgrade%20behavior%20is%20noted%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fgist.github.com%2F0xbadfca11%2Fda0598e47dd643d933dc%23mountability%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgist.github.com%2F0xbadfca11%2Fda0598e47dd643d933dc%23mountability%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1473343%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1473343%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F196768%22%20target%3D%22_blank%22%3E%40Michael%20Kiesel%3C%2FA%3E%26nbsp%3BHow%20old%20are%20we%20talking%20about%20here%3F%26nbsp%3B%20The%20biggest%20problem%20is%20there%20are%20some%20required%20CPU%20features%20to%20enable%20this%20support.%26nbsp%3B%20Depending%20on%20the%20age%2C%20this%20could%20prevent%20nested%20from%20working.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F696646%22%20target%3D%22_blank%22%3E%40proboszcz%3C%2FA%3E%26nbsp%3BYou%20asked%20a%20few%20questions%2C%20let%20me%20see%20if%20I%20can%20address%20each%20one.%3C%2FP%3E%0A%3CP%3EWhen%20will%20this%20feature%20be%20released%3A%20Our%20plan%20is%20to%20release%20it%20in%20future%20versions%20of%20Windows%20%26amp%3B%20Server%20but%20I'm%20not%20going%20to%20give%20a%20committed%20plan%20just%20yet%20as%20we%20need%20to%20get%20feedback%20and%20telemetry%20with%20the%20current%20implementation%20to%20see%20how%20much%20more%20work%20needs%20to%20be%20done.%26nbsp%3B%20Said%20another%20way%2C%20as%20of%20right%20now%2C%20yes%2C%20but%2C%20it's%20not%20a%20100%25%20yes.%3C%2FP%3E%0A%3CP%3ERe%3A%20earlier%20versions%20-%20We're%20looking%20to%20backport%20this%20to%20Windows%20Server%202019%20but%20don't%20have%20a%20committed%20date%20on%20that%20yet.%3C%2FP%3E%0A%3CP%3EAs%20for%20enlightenments%2C%20let%20me%20check%20with%20the%20team.%20I'll%20post%20an%20update%20here%20when%20I%20get%20an%20answer.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3EUsing%20the%20feedback%20hub%20is%20the%20best%20place%20for%20bugs%20as%20there%20are%20options%20for%20people%20to%20share%20logs%20there%20and%20it%20goes%20right%20into%20our%20bug%20tracking%20database.%26nbsp%3B%20For%20everything%20else%2C%20you%20can%20post%20here%2C%20uservoice%2C%20or%20feedback%20hub.%26nbsp%3B%20Note%2C%20I'll%20likely%20be%20checking%20here%20the%20most%20so%20take%20that%20into%20account.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F695385%22%20target%3D%22_blank%22%3E%40jcxerox%3C%2FA%3E%26nbsp%3BSome%20folks%20over%20on%20Github%20got%20the%20android%20emulator%20to%20work.%20Also%20the%20emulator%20team%20is%20aware%20of%20the%20feature%20reaching%20this%20level%20of%20maturity.%26nbsp%3B%20They%20haven't%20shared%20when%20their%20support%20gets%20into%20an%20Insider%20build%20but%20I%20can%20say%20they're%20excited%20as%20this%20is%20a%20highly%20desired%20feature%20for%20them.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1473381%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1473381%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F676358%22%20target%3D%22_blank%22%3E%40chuybregts%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20very%20much%20for%20your%20answers!%3C%2FP%3E%3CP%3EI%20will%20then%20be%20waiting%20for%20more%20information%20about%20the%20planned%20release%20and%20backporting%20of%20this%20feature%20from%20you%20then.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20my%20own%20testing%20I%20can%20tell%20that%20for%20now%20everything%20is%20working%20just%20fine%20except%20the%2032bit%20Windows%20when%20launched%20as%20a%20Level%202%20guest%20from%2064%20bit%20level%201%20guest.%20All%20my%20attempts%20ends%20up%20with%20a%20BSOD%20with%20%3CSPAN%3ETRAP_CAUSE_UNKNOWN%20code.%20Except%20for%20that%20this%20feature%20seems%20to%20work%20quite%20stable%20-%20good%20work%20guys%20%3A)%3C%2Fimg%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20was%20even%20able%20to%20run%20old%2064bit%20Windows%20XP%20as%20a%20level%202%20guest%20%3A)%3C%2Fimg%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1473834%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1473834%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F676358%22%20target%3D%22_blank%22%3E%40chuybregts%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20response.%20Here%20is%20a%20post%20on%20Twitter%20where%20i%20made%20two%20screenshosts%20of%20the%20older%20Processor%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2Fexcelsi84%2Fstatus%2F1273128417429512193%3Fs%3D20%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftwitter.com%2Fexcelsi84%2Fstatus%2F1273128417429512193%3Fs%3D20%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1476011%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1476011%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F626955%22%20target%3D%22_blank%22%3E%40kwinz%3C%2FA%3E%26nbsp%3BWe've%20spent%20a%20lot%20of%20time%20working%20on%20the%20best%20way%20to%20offer%20compatibility%20with%203rd%20party%20virtualization%20software%20running%20directly%20in%20the%20root%20partition.%26nbsp%3B%20Our%20solution%20is%20the%20Windows%20Hypervisor%20Platform%20API.%26nbsp%3B%20See%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fvirtualization%2Fapi%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fvirtualization%2Fapi%2F%3C%2FA%3E%26nbsp%3Band%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fvirtualization%2Fapi%2Fhypervisor-platform%2Fhypervisor-platform%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fvirtualization%2Fapi%2Fhypervisor-platform%2Fhypervisor-platform%3C%2FA%3E.%26nbsp%3B%20This%20powerful%20interface%20has%20proven%20to%20be%20very%20flexible%20and%20has%20already%20been%20adopted%20by%20major%20software%20vendors%20including%20VMware.%26nbsp%3B%20See%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fblogs.vmware.com%2Fworkstation%2F2020%2F05%2Fvmware-workstation-now-supports-hyper-v-mode.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.vmware.com%2Fworkstation%2F2020%2F05%2Fvmware-workstation-now-supports-hyper-v-mode.html%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1479028%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1479028%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20do%20I%20upgrade%20a%20Hyper-V%20VM%20from%209.0%20to%209.3%20so%20I%20can%20finally%20leverage%20this%20fix%3F%20It%20appears%20that%20this%20is%20the%20last%20step%20before%20I%20can%20finally%20successfully%20run%26nbsp%3B%3C%2FP%3E%3CPRE%3ESet-VMProcessor%20-VMName%20%26lt%3BVMName%26gt%3B%20-ExposeVirtualizationExtensions%20%24true%3C%2FPRE%3E%3CP%3Eon%20my%20vm%20so%20that%20I%20can%20leverage%20nested%20virtualization%20(Finally%20be%20able%20to%20use%20Docker%20inside%20my%20vm)%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20using%20an%20AMD%20Ryzen%205%203600%20CPU%20and%20currently%20running%20a%20Windows%2010%20Pro%20Hyper-V%20VM%20inside%20my%20Windows%2010%20Pro%20OS.%20Both%20are%20on%20preview%20build%2020150%20and%20the%20VM%26nbsp%3B%20is%20version%209.0%20Gen%202%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHopefully%20someone%20can%20point%20me%20in%20the%20right%20direction.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1480532%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1480532%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F705677%22%20target%3D%22_blank%22%3E%40efleming320%3C%2FA%3E%3C%2FP%3E%3CP%3ESee%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fhyper-v%2Fupdate-vmversion%3Fview%3Dwin10-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fhyper-v%2Fupdate-vmversion%3Fview%3Dwin10-ps%26nbsp%3B%3C%2FA%3Eif%20that%20works%2C%20else%20you'll%20need%20to%20create%20a%20new%20VM%20apparently%20for%20now%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2FBrucerVisor%2Fstatus%2F1270166131957891073%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftwitter.com%2FBrucerVisor%2Fstatus%2F1270166131957891073%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1482364%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1482364%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F676358%22%20target%3D%22_blank%22%3E%40chuybregts%3C%2FA%3E%26nbsp%3B%20%26nbsp%3BHow%20do%20I%20get%20this%20onto%20current%20windows%2010%20pro-2004%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20want%20to%20upgrade%20the%20entire%20base%20operating%20system%20to%20an%20insiders%20build.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20an%20update%20to%20the%20underlying%20hyper-v%20hypervisor%3B%20There%20most%20be%20a%20way%20of%20merely%20patching%20the%20hypervisor%20without%20moving%20the%20entire%20OS%20to%20an%20insiders%20build%3F%3C%2FP%3E%3CP%3ECome%20on%20MS%2C%20we%20are%20hurting%20for%20this%20feature%20and%20want%20it%20delivered%20via%20a%20windows%20update.%20Not%20an%20insiders%20build%20update%20that%20will%20take%201-2%20years%20to%20hit%20the%20mainstream.%3C%2FP%3E%3CP%3EJust%20want%20to%20patch%20the%20HV%20on%20my%20windows%20pro%202004%2C%20don't%20even%20need%20to%20update%20the%20GUI%20on%20HV%20management%20tools%2C%20because%20as%20far%20as%20I%20can%20tell%2C%20the%20expose%20CPU%20extensions%20is%20done%20via%20PowerShell%20on%20the%20VM%20itself.%20HV%20just%20needs%20to%20support%20SVM%20passthrough%20on%20the%20underlying%20hypervisor.%3C%2FP%3E%3CP%3EWhy%20is%20this%20update%20an%20insider%20build%20patch%3F%3F%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eis%20there%20anyway%2C%20official%20or%20unofficial%2C%20I%20can%20update%20my%20underlying%20hyper-v%20hypervisor%2C%20that's%20sit's%20underneath%20my%20windows%2010%20pro%202004%20install%2C%20to%20get%20Nested%20under%20AMD%20to%20pass%20through%2C%20without%20moving%20the%20whole%20system%20to%20a%20windows%20insiders%20build%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1532076%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1532076%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20updated%20my%20gear%20to%20AMD%20from%20Intel%20and%20few%20VMs%20arent%20working%20because%20of%20this%20%3A(%3C%2Fimg%3E%20%2C%20for%20now%20i%20turned%20off%20nested%20virtualization%20because%20I%20dont%20want%20to%20update%20my%20main%20rig%20to%20fast%20track.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1532428%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1532428%22%20slang%3D%22en-US%22%3E%3CP%3Elack%20of%20nested%20Virt%20was%20the%20sole%20reason%20holding%20me%20back%20from%20getting%20a%20Ryzen%203950X.%26nbsp%3B%20It%20is%20defo%20good%20news%20that%20this%20is%20now%20supported%2C%20although%20within%20the%20insider%20arena%20at%20this%20stage.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1535053%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1535053%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F733245%22%20target%3D%22_blank%22%3E%40roozbeh18%3C%2FA%3E%26nbsp%3Byou%20don't%20have%20to%20update%20you%20main%20rig%20to%20insider%20builds%20-%20you%20can%20use%20Native%20VHD%20Boot%20feature%20to%20have%20a%20separate%20OS%20with%20insider%20builds%20for%20that%20purpose.%20Thanks%20to%20that%20you%20will%20have%20your%20main%20OS%20untouched%20and%20can%20switch%20between%20the%20main%20OS%20and%20the%20insider%20one%20during%20the%20boot%20time.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1535093%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1535093%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F696646%22%20target%3D%22_blank%22%3E%40proboszcz%3C%2FA%3E%26nbsp%3BThanks%20for%20the%20information%2C%20I%20have%20set%20up%20a%20double%20boot%20with%20native%20vhd%20boot%20and%20an%20Insider%20track%20installed%20on%20VHD%20%2B%20my%20C%20drive%20as%20my%20main%20OS.%3C%2FP%3E%3CP%3EI%20have%20found%20that%20after%20using%20it%20a%20few%20times%20to%20test%20it%20out%2C%20it%20works%20OK%2C%20but%20is%20far%20far%20from%20ideal.%20I%20feel%20separated%20from%20my%20Main%20OS%20when%20I%20am%20in%20a%20Dual%20Boot%20environment.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20a%20bit%20disingenuous%20to%20state%20that%20you%20are%20not%20switching%20your%20main%20rig%20over%2C%20Right%3F%3C%2FP%3E%3CP%3EI%20mean%2C%20it%20does%20keep%20your%20%22Main%20OS%22%20Intact%2C%20but%20otherwise%2C%20it's%20a%20complete%20change%20that%20introduces%20additional%20problems.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3Ewhat%20about%20all%20your%20files%2C%20your%20settings%2C%20everything%20being%20remapped%20to%20D%3A%2C%20all%20your%20program%20install's%2C%20and%20an%20ever-expanding%20VHD%20taking%20up%20all%20your%20precious%20space%20on%20your%20SSD%3F%26nbsp%3B%3C%2FLI%3E%3CLI%3EAnd%20dual-booting%20between%20OS's%20means%20you%20will%20never%20be%20able%20to%20pick%20up%20where%20you%20just%20left%20off%3F%3C%2FLI%3E%3CLI%3EProblems%20with%20hibernate%2Fsuspend%2Fresume%3F%3C%2FLI%3E%3CLI%3EPermissions%20HELL%20where%20there%20are%20unknown%20users%20with%20permissions%20in%20either%20OS%3F%3C%2FLI%3E%3CLI%3EWindows%20Insiders%20cannot%20be%20updated%20inside%20a%20VHD%20Boot.%20For%20some%20unknown%20reason.%3C%2FLI%3E%3CLI%3EOne%20needs%20to%20hack%20with%20Hyperv%20VM%20on%20the%20Main%20OS%20side%2C%20boot%20up%20the%20Hyper-V%20VHD%20in%20a%20VM%20on%20the%20Main%20OS%20Side%2C%20to%20update.%3C%2FLI%3E%3CLI%3EThis%20introduces%20activation%20and%20Licence%20Hell%2C%20as%20windows%20belives%20the%20hardware%20has%20changed.%3C%2FLI%3E%3CLI%3EAnd%20on...%20and%20on...%20and%20on...%20lots%20of%20niggly%20issues%20with%20this%20approach.%3C%2FLI%3E%3CLI%3EIt%20really%20is%20not%20an%20ideal%20solution.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAmateur%20Opinion%20time%3A%3C%2FP%3E%3CP%3EIn%20My%20Very%20amateur%20and%20humble%20opinion%2C%20my%20understanding%20is%20the%20following%3A%3C%2FP%3E%3CP%3EHyper-V%20is%20a%20HyperVisor%20that%20sits%20%3CU%3E%3CSTRONG%3EUNDER%3C%2FSTRONG%3E%20%3C%2FU%3EWindows%2010.%20Windows%2010%20isn't%20even%20aware%20of%20it.%20The%20Hyper-V%20management%20tools%20such%20as%20Hyper-V%20manager%20connect%20to%20the%20underlying%20hypervisor%20via%20a%20socket%20on%20%3CU%3Ethe%20localhost%20network%20interface%20port.%3C%2FU%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWindows%20has%20nothing%20to%20do%20with%20this%20Hypervisor%20management.%20Hyper-V%20is%20its%20own%20things%20that%20sits%20underneath.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAgain%2C%20I%20am%20by%20no%20means%20a%20super%20expert%20on%20these%20things%2C%20but%20I%20just%20can't%20see%20why%20I%20cannot%20only%20update%20the%20Hyper-V%20underneath%20without%20moving%20to%20an%20insider%20build.%20Even%20the%20management%20tools%20do%20not%20need%20an%20update%2C%20as%20nested%20virtualisation%20%26amp%3B%20the%20VM%20Version%20is%20managed%20over%20flags%20and%20commands%20inside%20PowerShell.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhy%20can't%20I%20JUST%20update%20the%20Hyper-V%3F%3F%3F%3C%2FP%3E%3CP%3EManually%2C%20separately%2C%20like%20I%20do%20with%20the%20WSL2%20Linux%20Kernel%3F%3C%2FP%3E%3CP%3ECan%20anyone%20explain%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20very%20much.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1535135%22%20slang%3D%22en-US%22%3ERe%3A%20AMD%20Nested%20Virtualization%20Support%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1535135%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F707268%22%20target%3D%22_blank%22%3E%40Ameeno%3C%2FA%3E%26nbsp%3BI%20totally%20agree%20with%20you%20that%20this%20approach%20with%20Native%20VHD%20Boot%20is%20not%20ideal.%20But%20it%20is%20more%20nice%20than%20installing%20a%20second%20OS%20on%20a%20separate%20partition%20I%20think.%20Using%20such%20VHD%20you%20can%20very%20easily%20go%20from%20one%20PC%20to%20another%20with%20the%20same%20OS%20and%20its%20settings.%20However%20that%20comes%20at%20a%20cost%20you%20described.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F676358%22%20target%3D%22_blank%22%3E%40chuybregts%3C%2FA%3E%26nbsp%3Bcan%20you%20share%20with%20us%20an%20estimation%20when%20this%20feature%20will%20be%20added%20at%20least%20to%20a%20slow%20(Beta)%20ring%3F%20Forcing%20our%20main%20development%20rigs'%20OS%20into%20a%20fast%20(dev)%20ring%20is%20a%20very%20uncomfortable%20situation.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

AMD Nested Support showing a VM running on a VM on AMD HardwareAMD Nested Support showing a VM running on a VM on AMD Hardware

Nested Virtualization is not a new idea. In fact, we announced our first preview of Nested Virtualization running on Windows way back in 2015.  From that Windows Insider preview to now, Nested Virtualization has been used in a variety of offerings in a variety of ways.  Today, you can find Nested Virtualization support in Azure that gives the Azure users flexibility in how they want to setup their environments.  An example of Nested Virtualization being used to support our developer community is to accelerate Microsoft’s Android Emulation.  Nested Virtualization is being used by  IT Pros to set up a home labs. And we can’t forget containers! If you want to use a Hyper-V Containers inside a VM, you guessed it: this is enabled with Nested Virtualization.  You can start to see why Nested Virtualization is such a useful technology.

 

There is one group of users that was unable to take advantage of Nested Virtualization on Windows. These were our users with AMD hardware.  Not a week goes by where the team doesn’t get a request for Nested Virtualization support for AMD from our community or from within Microsoft.  In fact, it is the number 1 ask on Windows Server’s uservoice page. At the time of this blog post, it was almost 5x more than the next feedback item.

 

I am happy to announce that the community has been heard and starting with Windows Build 19636, you will be able to try out Nested Virtualization on AMD processors! If you’re on the Windows Insider Fast ring then you can try this out today.

 

As this is a preview release of Nested Virtualization on AMD, there are some guidance and limitations to keep in mind if you want to try this out.

  • Ensure your OS build number is 19636 or greater
  • Right now, this has been tested on AMD’s first generation Ryzen/Epyc or newer processors
  • For maximum stability and performance use a Windows guest with an OS version that is greater than or equal to the host OS version (19636) for now.  Linux KVM guest support will be coming in the future
  • Create a version 9.3 VM. Here’s an example PowerShell command to ensure a version 9.3 VM is being used:  New-Vm -VMName “L1 Guest” -Version 9.3
  • Follow the rest of the steps in our public documentation

 

June 12, 2020 edit: changed wording around Guest OS recommendation.

22 Comments
Honored Contributor

Awesome news! Hyper-V is my favorite Hypervisor and the most powerful one.

Occasional Visitor

Where do we go to find, or monitor progress, with Hyper-V Default vSwitch enhancements or fixes?  It's still causing many bandwidth issues with certain wifi choosers, so it seems. Our team needs a fix. 

Senior Member

This is a wonderful news. However "Use a Windows guest with an OS version that is greater than or equal to the host OS version (19636) for now. " is not a correct statement in my opinion. I was able to successfully use Windows 10 1909 in the guest which is the version of Windows far below the 19636. From my own testing every 64 bit Windows operating system is working as a guest and it does not have to be newer than 19636.

Occasional Visitor

Kind of way overdue, but thank you Microsoft, this is a great day for large (and fast growing) segment of your users. Looking forward to this landing in stable builds...

 

@proboszcz  - I am guessing that is the usual "just in case" to cover all bases, plus with all the work on mixed hypervisors and Linux community, that soon we will have support for all weird mixes like VMware, KVM, and any old weird OS we can think of. But thanks for confirming it that quickly!

Microsoft

@proboszcz LpAdm is absolutely right.  We haven't validated the scenarios and performance on earlier versions of Windows.  In order to ensure a high performance, we have to have some enlightenments in the guest OSs.  This is also why we didn't bring up Linux support yet.  We're still working on some enlightenments there.  Once we have that, I'll make another post to share with the community at large.  Keep trying things out!

 

Chris

Occasional Visitor

Now please enable me to use nested virtualization in the root domain (in Windows). This is the last puzzle piece that keeps me from upgrading to WSL2. 

Senior Member

@LpAdm @chuybregts , I totally agree with you. However I think it would be better to change that statement to something like this : "For maximum stability and performance use a Windows guest with an OS version that is greater than or equal to the host OS version (19636) for now" which will be more precise, because the current one suggests that using older versions of Windows will not work at all, which is not the case.

New Contributor

Please enable this also for older AMD Processors!

Senior Member

@chuybregts Can you tell us if this feature is planned to be included in Windows 10 20H2 final release? Also what about Windows Server 2019 - is it planned to be included to it or have we wait till the next big Windows Server 2022 version?

You also told something about enlightenments that should be included in level1 guest os for full performance. Will those enlightenments be propagated to earlier versions of Windows like Windows 10 1909, Windows Server 2019, etc.?

 

Is there a dedicated place where we can share our experience with this feature (report bugs, compatibility, etc) or should we do this here in the comments and Feedback Hub?

Occasional Visitor

Thank you for adding nested virtualization for AMD!!  Now if I could only get my android emulator to work in nested mode... but that's another story.

 

REFS heads up:  During the upgrade your writable REFS volumes will be upgraded to REFS version 3.5 and will not be readable prior to any build before 19536 (which includes 2004/19041 and earlier builds).  When reverting your build, you'll lose access to your REFS volumes.  REFS volume upgrade behavior is noted here: https://gist.github.com/0xbadfca11/da0598e47dd643d933dc#mountability

Microsoft

@Michael Kiesel How old are we talking about here?  The biggest problem is there are some required CPU features to enable this support.  Depending on the age, this could prevent nested from working.

 

@proboszcz You asked a few questions, let me see if I can address each one.

When will this feature be released: Our plan is to release it in future versions of Windows & Server but I'm not going to give a committed plan just yet as we need to get feedback and telemetry with the current implementation to see how much more work needs to be done.  Said another way, as of right now, yes, but, it's not a 100% yes.

Re: earlier versions - We're looking to backport this to Windows Server 2019 but don't have a committed date on that yet.

As for enlightenments, let me check with the team. I'll post an update here when I get an answer.  

Using the feedback hub is the best place for bugs as there are options for people to share logs there and it goes right into our bug tracking database.  For everything else, you can post here, uservoice, or feedback hub.  Note, I'll likely be checking here the most so take that into account.  

 

@jcxerox Some folks over on Github got the android emulator to work. Also the emulator team is aware of the feature reaching this level of maturity.  They haven't shared when their support gets into an Insider build but I can say they're excited as this is a highly desired feature for them.

Senior Member

@chuybregts 

Thank you very much for your answers!

I will then be waiting for more information about the planned release and backporting of this feature from you then. 

 

From my own testing I can tell that for now everything is working just fine except the 32bit Windows when launched as a Level 2 guest from 64 bit level 1 guest. All my attempts ends up with a BSOD with TRAP_CAUSE_UNKNOWN code. Except for that this feature seems to work quite stable - good work guys :)

I was even able to run old 64bit Windows XP as a level 2 guest :)

New Contributor

@chuybregts 

Thanks for your response. Here is a post on Twitter where i made two screenshosts of the older Processor:

https://twitter.com/excelsi84/status/1273128417429512193?s=20 

 

Microsoft

@kwinz We've spent a lot of time working on the best way to offer compatibility with 3rd party virtualization software running directly in the root partition.  Our solution is the Windows Hypervisor Platform API.  See: https://docs.microsoft.com/en-us/virtualization/api/ and https://docs.microsoft.com/en-us/virtualization/api/hypervisor-platform/hypervisor-platform.  This powerful interface has proven to be very flexible and has already been adopted by major software vendors including VMware.  See: https://blogs.vmware.com/workstation/2020/05/vmware-workstation-now-supports-hyper-v-mode.html

Occasional Visitor

How do I upgrade a Hyper-V VM from 9.0 to 9.3 so I can finally leverage this fix? It appears that this is the last step before I can finally successfully run 

Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true

on my vm so that I can leverage nested virtualization (Finally be able to use Docker inside my vm) 

 

I am using an AMD Ryzen 5 3600 CPU and currently running a Windows 10 Pro Hyper-V VM inside my Windows 10 Pro OS. Both are on preview build 20150 and the VM  is version 9.0 Gen 2

 

Hopefully someone can point me in the right direction.

Occasional Visitor
Occasional Visitor

@chuybregts   How do I get this onto current windows 10 pro-2004?

 

I don't want to upgrade the entire base operating system to an insiders build.

 

It is an update to the underlying hyper-v hypervisor; There most be a way of merely patching the hypervisor without moving the entire OS to an insiders build?

Come on MS, we are hurting for this feature and want it delivered via a windows update. Not an insiders build update that will take 1-2 years to hit the mainstream.

Just want to patch the HV on my windows pro 2004, don't even need to update the GUI on HV management tools, because as far as I can tell, the expose CPU extensions is done via PowerShell on the VM itself. HV just needs to support SVM passthrough on the underlying hypervisor.

Why is this update an insider build patch????

 

is there anyway, official or unofficial, I can update my underlying hyper-v hypervisor, that's sit's underneath my windows 10 pro 2004 install, to get Nested under AMD to pass through, without moving the whole system to a windows insiders build??

Occasional Visitor

Just updated my gear to AMD from Intel and few VMs arent working because of this :( , for now i turned off nested virtualization because I dont want to update my main rig to fast track.

Occasional Visitor

lack of nested Virt was the sole reason holding me back from getting a Ryzen 3950X.  It is defo good news that this is now supported, although within the insider arena at this stage. 

Senior Member

@roozbeh18 you don't have to update you main rig to insider builds - you can use Native VHD Boot feature to have a separate OS with insider builds for that purpose. Thanks to that you will have your main OS untouched and can switch between the main OS and the insider one during the boot time.

Occasional Visitor

@proboszcz Thanks for the information, I have set up a double boot with native vhd boot and an Insider track installed on VHD + my C drive as my main OS.

I have found that after using it a few times to test it out, it works OK, but is far far from ideal. I feel separated from my Main OS when I am in a Dual Boot environment.

 

It is a bit disingenuous to state that you are not switching your main rig over, Right?

I mean, it does keep your "Main OS" Intact, but otherwise, it's a complete change that introduces additional problems.

 

  • what about all your files, your settings, everything being remapped to D:, all your program install's, and an ever-expanding VHD taking up all your precious space on your SSD? 
  • And dual-booting between OS's means you will never be able to pick up where you just left off?
  • Problems with hibernate/suspend/resume?
  • Permissions HELL where there are unknown users with permissions in either OS?
  • Windows Insiders cannot be updated inside a VHD Boot. For some unknown reason.
  • One needs to hack with Hyperv VM on the Main OS side, boot up the Hyper-V VHD in a VM on the Main OS Side, to update.
  • This introduces activation and Licence Hell, as windows belives the hardware has changed.
  • And on... and on... and on... lots of niggly issues with this approach.
  • It really is not an ideal solution.

 

Amateur Opinion time:

In My Very amateur and humble opinion, my understanding is the following:

Hyper-V is a HyperVisor that sits UNDER Windows 10. Windows 10 isn't even aware of it. The Hyper-V management tools such as Hyper-V manager connect to the underlying hypervisor via a socket on the localhost network interface port.

 

Windows has nothing to do with this Hypervisor management. Hyper-V is its own things that sits underneath.

 

Again, I am by no means a super expert on these things, but I just can't see why I cannot only update the Hyper-V underneath without moving to an insider build. Even the management tools do not need an update, as nested virtualisation & the VM Version is managed over flags and commands inside PowerShell.

 

Why can't I JUST update the Hyper-V???

Manually, separately, like I do with the WSL2 Linux Kernel?

Can anyone explain?

 

Thanks very much.

Senior Member

@Ameeno I totally agree with you that this approach with Native VHD Boot is not ideal. But it is more nice than installing a second OS on a separate partition I think. Using such VHD you can very easily go from one PC to another with the same OS and its settings. However that comes at a cost you described.

 

@chuybregts can you share with us an estimation when this feature will be added at least to a slow (Beta) ring? Forcing our main development rigs' OS into a fast (dev) ring is a very uncomfortable situation.