ESX -HyperV

[nmd78641]

After migrating the VM, I noticed that all server NICs reset to defaults—is this normal? Also, once migration is complete, can files simply be copied from the temporary Hyper-V server to the newly formatted Hyper-V server without needing a v2v process?

[yaroslav (staff)]

Welcome to StarWind Forum

NICs reset to defaults—is this normal

Could you please expand on this bit?

Also, once migration is complete, can files simply be copied from the temporary Hyper-V server to the newly formatted Hyper-V server without needing a v2v process?

There's no need to copy anything. V2V does not alter the source data. It just takes a source disk and remaps it in a new format.
This means that the newly created disk will have whatever data was on the source VM or server, so no need to copy or use temporary storage.

[nmd78641]

Thank you for the reply on the ESX server the dc had a static ip once we ran the converter and booted it up on the Hyper V box went into control panel and the IP address on the nic was gone it was set to DHCP, so we had to reset the ip on the migrated DC to the correct one but got the this ip is in use on another adapter, rebooted and all is working fine currently as this is a simulated LAB before we do it in production.


The second question is based on today we have an esx server that we will convert and migrate the VMs to a temp Hyper V server, once they are converted and migrated we will then format and reload the old ESX server and load windows server with and add the hyper v roles to migrate the VM's back to the production server. Question is what is the recommended best practice to do this is it to run another V2V from the temp hyper v to the new hyper v, or can we simply copy the migrated disks to the production hyper v?

[nrowland]

Yes, the IP issue is expected. In VMWare you probably had a VMXNet3 or emulated Intel adapter. HyperV will create a HyperV adapter. Windows does not automatically translate the network configuration from one adapter to another. The Starwinds converter will not touch the OS, just translate the disk.

Also worth noting:
HyperV will inject additional drivers into the OS on the first boot, you'll want to restart a second time before things work properly.

[nmd78641]

Yes, the IP issue is expected. In VMWare you probably had a VMXNet3 or emulated Intel adapter. HyperV will create a HyperV adapter. Windows does not automatically translate the network configuration from one adapter to another. The Starwinds converter will not touch the OS, just translate the disk.

Also worth noting:
HyperV will inject additional drivers into the OS on the first boot, you'll want to restart a second time before things work properly.

Thank you for the update:

Any insight into this question below?
The second question is based on today we have an esx server that we will convert and migrate the VMs to a temp Hyper V server, once they are converted and migrated we will then format and reload the old ESX server and load windows server with and add the hyper v roles to migrate the VM's back to the production server. Question is what is the recommended best practice to do this is it to run another V2V from the temp hyper v to the new hyper v, or can we simply copy the migrated disks to the production hyper v?

[nrowland]

You can configure HyperV to do Live migrations natively, even if they aren't in a cluster. There may be some nuance to the networking setup or authentication setup depending on how you've done things. But generally you can enable Live Migrations on both boxes, make sure your virtual switches have the exact same name, and run the Move-VM command in Powershell.

[nmd78641]

You can configure HyperV to do Live migrations natively, even if they aren't in a cluster. There may be some nuance to the networking setup or authentication setup depending on how you've done things. But generally you can enable Live Migrations on both boxes, make sure your virtual switches have the exact same name, and run the Move-VM command in Powershell.

That will be an issue as our hosts are not joined to the domain, any other suggestions?

[nrowland]

You can supply the credentials manually, but if you're set on moving the files by hand: you don't need a V2V converter, you can just copy the folder (the whole folder) and use the "import VM" on the destination.

[yaroslav (staff)]

That's right: Hyper-V VM migration should do the trick.
Thanks for your help, @nrowland!

[nmd78641]

Thank you all for the help and responses and the tool.

[yaroslav (staff)]

Thanks for your cooperation. Good luck with your project!

[nmd78641]

Quick question converted a 2 VM's to a temp hyper v host as we needed to reload the current ESX server with windows.
We booted up the VMs on the temp hyper v host to make sure we could boot and test all is good.
The old server was reloaded and we copied the VM's from the temp Hyper V to the new Hyper V
We are going to import them but we want to make sure we select the correct option when importing.

2 machines converted one DC and one APP

We have the below options:
Register the VM in place (use existing unique ID)
Restore the VM ( use the existing unique ID)
Copy the VM (create a new unique ID)

We believe we should select Copy the VM (create a new unique ID) but would like some feedback please.

Copy the virtual machine: Recommended for moving a VM between hosts. It creates a new VM with a new unique ID, copies the VM files to the new host's default location, and lets you resolve hardware/network mismatches

[yaroslav (staff)]

Your request does not relate to V2V, but falls under the general Hyper-V questions. I can't advise on this matter.
From my experience, you can use Copy. The VM is new, and it will be nice to get the nice ID. Those IDs matter for things like backup jobs.

[nmd78641]

Thanks and understand, how about VMware tools should we remove those before conversion?

[yaroslav (staff)]

Yes, they need to be removed, otherwise they migth prevent the VM from starting at the destination.