No vmxnet3 adapter after V2V conversion

[whausner]

We have plans to use Veeams amazing V2V feature quite extensively. Having to convert thousands of VMs from Hyper-V to Vmware makes it necessary to have a well automated workflow. Though Veeams conversion feature works as expected we are not able to get the VM that is created under Vmware to use a vmxnet3 type of network adapter. Instead we get the standard E1000 no matter what. Even installing Vmware Tools before the conversion does not do the trick.

Are there any (hidden) options I've missed out on?

Converting the adapter afterwards creates lots of problems, like losing IP config.

[Mildur]

Do you have tried to convert it on PowerCLI?
If I remember correctly, the mac address and ip address do not change with that command.

Code: Select all

Get-VM <Virtual_Machine_name> | Get-NetworkAdapter | Set-NetworkAdapter -type vmxnet3 -confirm:$false

[whausner]

Yes, I have. This converts the adapter but still throws away the IP config. Btw. Vmware Support says not to use this PowerCLI function as it can cause problems later on with the network adapter.

[Mildur]

Yes, you are right. I see the same behaviour in my lab.

[whausner]

Thanks for testing out!