System repair when toggling expose nested virtualization

%3CLINGO-SUB%20id%3D%22lingo-sub-1527252%22%20slang%3D%22en-US%22%3ESystem%20repair%20when%20toggling%20expose%20nested%20virtualization%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1527252%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20running%20image%20backups%20of%20all%20my%20windows%20systems%20including%20Hyper-V%20installations.%20Most%20of%20the%20time%2C%20I%20can%20then%20later%20start%20virtual%20machines%20by%20just%20using%20the%20image%20as%20the%20OS%20disk.%20I%20can%20also%20enable%20nested%20virtualization%20and%20the%20run%20the%20existing%20vms%20in%20an%20extra%20sandbox%20or%20export%20them.%3C%2FP%3E%3CP%3ENow%20I%20installed%20a%20new%20Hyper-V%20system%20using%20a%20newer%20refresh%20DVD%20from%20evaluation%20center.%20Unfortunately%20for%20that%20version%20enabling%20nested%20virtualization%20causes%20Hyper-V%20to%20go%20into%20repair%20mode%20(no%20clue%20what%20I%20should%20repair%20then).%20Any%20idea%20why%3F%3C%2FP%3E%3CP%3EBoth%20systems%20claim%20to%20be%2010.0.17763%20N%26amp%3BA%20Build%2017763%2C%20but%20differ%20in%20the%20hotfixes%20listed.%20Drivers%20should%20be%20equivalent%20for%20OEM%20drivers%2C%20but%20for%20built-ins%20don%C2%B4t%20know.%3C%2FP%3E%3CP%3EAny%20idea%3F%3C%2FP%3E%3CP%3EIt%20is%20very%20convenient%20to%20know%20backups%20run%20virtually%2C%20and%20the%20fact%20that%20it%20does%20not%20work%20not%20just%20irritates%20but%20worries%20me.%3C%2FP%3E%3CP%3EThanks%2C%20Joachim%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1527252%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Contributor

I am running image backups of all my windows systems including Hyper-V installations. Most of the time, I can then later start virtual machines by just using the image as the OS disk. I can also enable nested virtualization and the run the existing vms in an extra sandbox or export them.

Now I installed a new Hyper-V system using a newer refresh DVD from evaluation center. Unfortunately for that version enabling nested virtualization causes Hyper-V to go into repair mode (no clue what I should repair then). Any idea why?

Both systems claim to be 10.0.17763 N&A Build 17763, but differ in the hotfixes listed. Drivers should be equivalent for OEM drivers, but for built-ins don´t know.

Any idea?

It is very convenient to know backups run virtually, and the fact that it does not work not just irritates but worries me.

Thanks, Joachim

 

 

0 Replies