Nest Virtualization - HyperV Networking issue

%3CLINGO-SUB%20id%3D%22lingo-sub-3372507%22%20slang%3D%22en-US%22%3ENest%20Virtualization%20-%20HyperV%20Networking%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3372507%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIm%20curious%20if%20anyone%20else%20has%20run%20into%20this%20issue%2C%20and%20if%20there%20are%20any%20known%20solutions.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20template%20that%20I've%20published%2C%20the%20VM%20is%20using%20nested%20virtualization%20with%20hyper%20V%2C%20I%20followed%20the%20documentation%20for%20creating%20the%20nested%20environment%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Flab-services%2Fhow-to-enable-nested-virtualization-template-vm-ui%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Flab-services%2Fhow-to-enable-nested-virtualization-template-vm-ui%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20when%20a%20student%20starts%20a%20VM%20from%20this%20template%2C%20it%20appears%20the%20network%20configuration%20is%20messed%20up.%20ipconfig%20only%20shows%20the%20NIC%20for%20the%20virtual%20switch%2C%20but%20not%20the%20%22ethernet%22%20adapter%20that's%20connected%20to%20the%20HyperV%20host.%20However%2C%20looking%20at%20the%20adapter%20settings%20I%20see%20the%20adapter%20is%20enabled.%20Routing%20and%20Remote%20Access%20does%20not%20list%20the%20adapters%20in%20the%20NAT%20configuration%2C%20wherass%20the%20template%20VM%20does.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20assumption%20is%20that%20something%20happens%20with%20the%20virtual%20NIC%20on%20the%20root%2Fparent%20HyperV%20host%20when%20it%20gets%20created%20from%20the%20template.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi All,

 

Im curious if anyone else has run into this issue, and if there are any known solutions. 

 

I have a template that I've published, the VM is using nested virtualization with hyper V, I followed the documentation for creating the nested environment here: https://docs.microsoft.com/en-us/azure/lab-services/how-to-enable-nested-virtualization-template-vm-...

 

However, when a student starts a VM from this template, it appears the network configuration is messed up. ipconfig only shows the NIC for the virtual switch, but not the "ethernet" adapter that's connected to the HyperV host. However, looking at the adapter settings I see the adapter is enabled. Routing and Remote Access does not list the adapters in the NAT configuration, wherass the template VM does. 

 

My assumption is that something happens with the virtual NIC on the root/parent HyperV host when it gets created from the template. 

0 Replies