Is the VM poweredoff when you change the NIC type ?
it's still poweredon.
And did you try it with the VM powered off ?
I think the VM needs to be powered off to change the NIC Type.
It's like you said Luc. But i am surprised with the result. When vm is powered off, set-networkadapter to different type acts in the same way like when vm is powered on(no errors as well). When the vm will be powered up after, all network information is lost.
I am just wondering if this infrmation shouldn't be put into the manual , i mean how come should i know that this action will clear my network information, or how come in powercli it does not throw any error when vm is powered on ? Maybe help for this cmdlet should be updated, it leaves to many things open, does not say in front that:
1. please shut down vm first, if should say : invalid vm state when it's powered on
2. big sign that this will make the interface to loose network config .
I agree, the cmdlet should be a bit more user friendly, and the conditions and effects should be mentioned in the help.
1 person found this helpful
Thanks for the notice guys. We'll take care to update the documentation as needed.
Some more info is required in order to reproduce the issue:
1. What's your VC version?
2. What's your PowerCLI version?
3. What's the hardware version of the VM?
4. What are the lost settings?
5. Is it correct that you are trying to perform an e1000 to vmxnet3 transformation?
VC 5.0.0 build 755629
VMware vSphere PowerCLI 5.0.1 build 581491
VMware AutoDeploy PowerCLI Component 5.0 build 544967
VMware ImageBuilder PowerCLI Component 5.0 build 544967
VMware vCloud Director PowerCLI Component 1.5 build 581492
VMware License PowerCLI Component 5.0 build 544881
VMware vSphere PowerCLI Component 5.0 build 581435
VM version 7
If this operation is done while vm is powered off, windows acts in the way as it would found a new network card, hence ALL network settings regarding that old e1000 are not there.
e1000 -> vmxnet3
Thanks for the quick reply.
Have you tried the same operation with the latest build of PowerCLI? If you've been able to reproduce the issue with the latest build, we'll investigate further. Up to now, using PowerCLI 5.1R1 we haven't been able to reproduce the issue. If the problem is only reproducible in earlier versions of both PowerCLI and VC, the options for fixing or documenting it are limited.
Sure thing Iva, i will test that using newest release of powercli and get back to you with feedback
Did you have the chance to check this?
i have installed latest powercli. On windows 2008 r2, while vm was powered on i have added an e1000 nic, then i used set-networkadapter cmdlet to convert it to vmxnet3. Command ran without issues, in the system e1000 is still present even after reboot. It's the same behaviour when previous version of PowerCLI was used.
In the configuration of vm, when you look at edit settings, that nic is presented as vmxnet 3. But OS is not noticing this fact.
I also made a test on a vm which is powered off. The same results as previously. Nic is changed to vmxne3, OS recognizes it as a new vmxnet3 nic, and it defaults the settings to use the DHCP.
If you are having different results, can you share how are you doing this ? Maybe i am testing it in wrong way ?