Hyper-V 2019 not finding network cards, but... they work and are there when loading the vm in 2016

%3CLINGO-SUB%20id%3D%22lingo-sub-211119%22%20slang%3D%22en-US%22%3EHyper-V%202019%20not%20finding%20network%20cards%2C%20but...%20they%20work%20and%20are%20there%20when%20loading%20the%20vm%20in%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-211119%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20trying%20to%20put%20some%2017629%20server%20into%20use%20to%20see%20the%20performance.%20For%20that%20I%20exported%20some%20of%20my%20development%20VM's%2C%20copied%20them%20over%20and%20imported%20them%20into%20the%20new%20cluster.%20They%20are%20exported%20from%20a%202016%20server.%20Gen%202%2C%20config%20version%208.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20import%20they%20loose%20the%20network%20card%20configuration.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20take%20the%20same%20export%2C%20copy%20it%20on%20a%20Win%202016%20and%20a%20Win%202019%26nbsp%3Bcluster%20(just%20saying%2C%20maybe%20it%20is%20the%20cluster%3F)%20machine.%20Import%20the%20same%20image%20on%20both%20(through%20simple%20registration).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E*%20Win%202016%20shows%20me%20one%20network%20adapter%20is%20there%3C%2FP%3E%3CP%3E*%20Win%202019%20shows%20me%20no%20network%20adapter%20present.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eget-vmnetworkadapter%20shows%20the%20same.%20Simply%20no%20adapter%20present.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20start%20the%20WIn%202019%20version%20(it%20is%20a%202016%20server%20core)%20and%20do%20some%20commandline...%20lo%20and%20behold%2C%20the%20network%20card%20is%20still%20there.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESomething%20is%20not%20handling%20this%20well.%20Now%20I%20have%20a%20configuraiton%20I%20can%20not%20change%20(including%20changing%20switches%2C%20VLAN%20ID)%20in%20Hyper-V%20but%20the%20NIC%20is%20active.%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-211119%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EClustering%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ENetworking%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

I am trying to put some 17629 server into use to see the performance. For that I exported some of my development VM's, copied them over and imported them into the new cluster. They are exported from a 2016 server. Gen 2, config version 8.

 

 

After import they loose the network card configuration.

 

I take the same export, copy it on a Win 2016 and a Win 2019 cluster (just saying, maybe it is the cluster?) machine. Import the same image on both (through simple registration).

 

* Win 2016 shows me one network adapter is there

* Win 2019 shows me no network adapter present.

 

get-vmnetworkadapter shows the same. Simply no adapter present.

 

I start the WIn 2019 version (it is a 2016 server core) and do some commandline... lo and behold, the network card is still there.

 

Something is not handling this well. Now I have a configuraiton I can not change (including changing switches, VLAN ID) in Hyper-V but the NIC is active.

 

 

0 Replies
www.000webhost.com