Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 230663

Re: PowerCli Migration from E1000 to vmxnet3 issues

$
0
0

The problem is that Windows (or another OS, we had the same thing come up with a Linux VM during a course, when we tried this shortcut with PowerCLI) doesn't load the appropriate driver for the new device when you perform the switch "live"; it doesn't recognize that the device has changed. Now to add to the mess, Windows will probably see the NIC as a different device after a reboot, hence the steps that were mentioned by LucD. You might even have to find and delete the "old" NIC, which doesn't exist any more as well in Windows (known issue when converting/importing VMs as well). The guest OS'es obviously cannot keep up with the changes you can perform on the VMware level.


Viewing all articles
Browse latest Browse all 230663

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>