Unable to convert VMware VMs to Hyper-V VMs

Question

Good morning,

So I'm at last on my final steps validating Hyper-V and now I'm testing the SCVMM conversion tool.

Since it's a lab environment I just have this very basic out-of-the-box configuration both for VMware and Hyper-V.

Hyper-V environment is based on 3 hosts running Hyper-V, Failover Clustering and S2D and 1 SCVMM instance (all 22 versions).

VMware environment is just a single host connected to a vCenter Server (all vSphere 8).

I managed to connect both vCenter and the ESXi host successfully to SCVMM. The issue starts when I try the conversion.

When I reach the "Destination Host" step I get this "No available connection to the selected VM network can be found" and therefore I'm unable to continue.

Searching online I only found some extremely shallow information saying that I "should go to Fabric > Logical Networks and 'configure the network'".

What I don't understand is which network exactly we're talking about here since I did not find any documentation on network prerequisites for this process.

Also, when I go to Fabric > Logical Networks and VMs and Services > VM Networks all I see is the virtual switch that was imported from vSphere.

I noticed that the Hyper-V hosts virtual switches do not show in any of those sections although they are created at the hosts.

I tried doing things like configuring "Site" and "IP Pools" on the Logical Network (not exactly sure how that would help) and there's absolutely nothing to configure for the VM Network. Tried renaming all networks to have the exact same name on vSphere and Hyper-V, tried creating new Logical/VM Networks, restarting SCVMM but nothing worked.

What exactly am I missing here?

Answer 1

Ok, I found it.

Just to mention that all directions (articles and documentation) were completely WRONG!!

What I needed to do was to enable the network imported from VMware on the Hyper-V host physical NIC that is using the Hyper-V virtual switch I mentioned above.

We do that by going to VMs and Services, locating the host to where I want to convert the VMware VM, Right-click it > Properties > Hardware > physical NIC configured for the Hyper-V virtual switch > Logical Network Connectivity > Check the VMware imported network.

Now the host complies with the check for conversion.

(I also had a "Virtual Machine Manager cannot contact <esxi host> because the credentials for <esxi host> are missing." but the credentials in this case was the certificate, not user credentials).

Now the conversion is going smoothly.

Answer 2

Hello! I'm sorry to hear that you're having trouble converting VMware VMs to Hyper-V VMs using the SCVMM conversion tool. Based on the error message you received, it seems that there might be an issue with the network configuration.

To resolve this issue, you can try the following steps:

1. Make sure that the virtual switch on the Hyper-V host is configured correctly and is connected to the appropriate physical network adapter.

2. Check the network settings on the VMware VMs to ensure that they are configured correctly and are connected to the appropriate virtual network.

3. In SCVMM, go to Fabric -> Logical Networks and make sure that the logical network is configured correctly and is connected to the appropriate physical network adapter.

4. In SCVMM, go to Fabric -> VM Networks and make sure that the VM network is configured correctly and is connected to the appropriate logical network.

5. Try renaming the logical network and VM network to have the exact same name on both vSphere and Hyper-V.

If none of these steps work, you may need to consult the SCVMM documentation for further assistance:

https://learn.microsoft.com/en-us/system-center/vmm/?view=sc-vmm-2022

Answer 3

So, what exactly do you mean with "appropriate"?

Because I have the most simple configuration possible:

• On VMware, there's only one single network connected to only one single network adapter;
• On Hyper-V, there's only one single virtual switch created using only one single network adapter on the host;
• Everything is a flat network (no VLANs), so all VMware and Hyper-V hosts and all VMs are connected to the same network;
• I've already renamed everything to have the same name, and that did not work.

So once again I'm asking: What exactly am I missing here?

Because when the message "No available connection to the selected VM network can be found" I say: WHO does not have a connection to WHICH VM Network?

I already went through the whole documentation and there's basically nothing on the conversion process besides this link which is not helpful at all.

Answer 4

We appreciate your feedback and contacting the Microsoft Community