I have two hosts with local storage running Windows Server 2012 in a test domain.

From either of those hosts using Hyper-V manager I can migrate vm's to the other hosts.

I've been waiting for VMM 2012 sp1 to come out, and now that it has, and I have it installed, I cannot do a live migration from one host to the other.  I get the message above.

Can anyone advise what may be causing this?

Regards

Ian

Hello

Did you create the virtual machine network ?

Yes (but not using VMM, this is an existing pair of hosts created previously and set up using Hyper-V Manager on the respective hosts).

If I set the network connection to be not connected, then both hosts get a rating and I can migrate.

Ian

I have exactly the same probleme same message

"No available connection to selected VM Network can be found.

Ensure host NICs have connection to the fabric network on which VM Network is created.

ID: 23801"

My config is one VMware esx enterprise with Vcenter

one HyperV 2012.  Both have network card

one SCVMM 2012 with SP1

both can see each other

both have acces to internet.

The purpose of the exercise is to migrate from ESX to HyperV

can anyone help???

I have exactly the same probleme same message

"No available connection to selected VM Network can be found.

Ensure host NICs have connection to the fabric network on which VM Network is created.

ID: 23801"

My config is one VMware esx enterprise with Vcenter

one HyperV 2012.  Both have network card

one SCVMM 2012 with SP1

both can see each other

both have acces to internet.

The purpose of the exercise is to migrate from ESX to HyperV

can anyone help???

• Edited by Michel Monette Friday, January 25, 2013 1:58 PM

I have exactly the same probleme same message

"No available connection to selected VM Network can be found.

Ensure host NICs have connection to the fabric network on which VM Network is created.

ID: 23801"

My config is one VMware esx enterprise with Vcenter

one HyperV 2012.  Both have network card

one SCVMM 2012 with SP1

both can see each other

both have acces to internet.

The purpose of the exercise is to migrate from ESX to HyperV

can anyone help???

• Edited by Michel Monette Friday, January 25, 2013 1:58 PM

I have exactly the same probleme same message

"No available connection to selected VM Network can be found.

Ensure host NICs have connection to the fabric network on which VM Network is created.

ID: 23801"

My config is one VMware esx enterprise with Vcenter

one HyperV 2012.  Both have network card

one SCVMM 2012 with SP1

both can see each other

both have acces to internet.

The purpose of the exercise is to migrate from ESX to HyperV

can anyone help???

• Edited by Michel Monette Friday, January 25, 2013 1:58 PM

Interestingly this is the reason I've set up a test domain, firstly to look at Hyper-V 3.0 but with the aim of migrating from VMWare too.

Would be nice to get a resolution to this quickly....sure it's something or nothing.

Regards

Ian

I am having the same problem. I get this error if i try to migrate a VM to another host.

Michel Monette, youll only migrate your vms from ESX to Hyper-v using the VCenter connection on SCVMM2012

But if the VMs in your ESX are ms windows , you can use the option "P2V - phisical to virtual" and it will work

Im doing it , and I migrated VMs from REV (red hat enterprise virtualization) to hyperv (server2012 + failover cluster + SAN storage)

Regards,

Thiago Beier

I dont use ESX only Hyper-v. I have vm networks in SCVMM and Logical networks.

I dont use ESX only Hyper-v. I have vm networks in SCVMM and Logical networks.

• Proposed as answer by Dean Gunraj Friday, March 29, 2013 3:30 PM
• Unproposed as answer by Dean Gunraj Friday, March 29, 2013 3:30 PM

I dont use ESX only Hyper-v. I have vm networks in SCVMM and Logical networks.

• Proposed as answer by Dean Gunraj Friday, March 29, 2013 3:30 PM
• Unproposed as answer by Dean Gunraj Friday, March 29, 2013 3:30 PM

I dont use ESX only Hyper-v. I have vm networks in SCVMM and Logical networks.

• Proposed as answer by Dean Gunraj Friday, March 29, 2013 3:30 PM
• Unproposed as answer by Dean Gunraj Friday, March 29, 2013 3:30 PM

Ian,

I think (not having the product myself, yet) the problem is on the network card on the VM. Try 'disconnecting' the NIC via SCVMM, save the configuration, and then try the migration. 

I suspect the reason is the networks are dissimilar, and when migrated, the box will not have a virtual switch to hook into.

Let me know if this helps.

I'm afraid not.  I disconnected the NIC on the VM as suggested.

However, when trying to Migrate, the rating for the remote host did not appear, although it did take quite some time to determine!!!

Cheers

Ian

Open the VMM console, click Fabric, right-click a host that has the error and click properties, click hardware, under Ethernet adapters select the proper logical network.

Open the VMM console, click Fabric, right-click a host that has the error and click properties, click hardware, under Ethernet adapters select the proper logical network.

• Proposed as answer by Dean Gunraj Friday, March 29, 2013 3:30 PM
• Unproposed as answer by Dean Gunraj Friday, March 29, 2013 3:30 PM

Open the VMM console, click Fabric, right-click a host that has the error and click properties, click hardware, under Ethernet adapters select the proper logical network.

• Proposed as answer by Dean Gunraj Friday, March 29, 2013 3:30 PM
• Unproposed as answer by Dean Gunraj Friday, March 29, 2013 3:30 PM

Open the VMM console, click Fabric, right-click a host that has the error and click properties, click hardware, under Ethernet adapters select the proper logical network.

• Proposed as answer by Dean Gunraj Friday, March 29, 2013 3:30 PM
• Unproposed as answer by Dean Gunraj Friday, March 29, 2013 3:30 PM

There are two things you have to perfrom to make this work.

1) Go to each Hyper-V or VMWare host machine and take host properties within SCVMM 2012 SP1 Management Console, and select the logical network created by SCVMM like 10.200.x.x/24 and bind them with the appropriate physical or teamed network.

2) Go to logical network section in the SCVMM Fabric Settings, and from there right click on your Hypervisor created network like the one which is created by Hyper-V and take the properties and check the box saying "Allow new VM networks created on this logical network to use network virtualization".

Now you have to select the virtual logical network created by SCVMM automatically to your VM template or new VM creation within SCVMM 2012 SP1.

I was having the similar problem and after doing this I fixed the problem. 

Cheers!

Unfortunately I've not had time to attempt the suggestions above, but am intending to recreate the hosts anyway, now that I am a bit more familiar.

I will bear the above in mind though especially if the same problems crop up.

Cheers

Zahir,

can you be more specific in your directions. I am new to this and I am not sure how to complete the steps you suggest.

Thanks you

Hi Zahir / All

I come access this issue when trying to migrate a Hyper V Virtual Machine from Windows Server 2008 R2 to Windows Server 2012 using SCVMM 2012. I spent a bit of time researching finding an easy way to get round it and finally just worked out a way myself by creating a new test machine, thought I would post the steps here;

1. Shut down the virtual machine you want to migrate.
2. In VMM 2012 > 'VM's and Services' Right click on the virtual machine, click properties.
3. Click "Hardware Configuration"
4. Scroll down to Network Adapters and choose, you network adapter.
5. Under connectivity, choose "Not Connected". Click ok.
6. You should then be able to migrate the virtual machine.
7. Once the migration is complete, go back into the Network Adapter properties.
8. Click "Connected to a VM network"
9. And choose a VM network available. I didn't worry about the VM Subnet section and just left it blank. Click ok
10. Turn on the virtual machine. Complete.

I recommend trying these steps out on a test environment first.

Hi Zahir / All

I come access this issue when trying to migrate a Hyper V Virtual Machine from Windows Server 2008 R2 to Windows Server 2012 using SCVMM 2012. I spent a bit of time researching finding an easy way to get round it and finally just worked out a way myself by creating a new test machine, thought I would post the steps here;

1. Shut down the virtual machine you want to migrate.
2. In VMM 2012 > 'VM's and Services' Right click on the virtual machine, click properties.
3. Click "Hardware Configuration"
4. Scroll down to Network Adapters and choose, you network adapter.
5. Under connectivity, choose "Not Connected". Click ok.
6. You should then be able to migrate the virtual machine.
7. Once the migration is complete, go back into the Network Adapter properties.
8. Click "Connected to a VM network"
9. And choose a VM network available. I didn't worry about the VM Subnet section and just left it blank. Click ok
10. Turn on the virtual machine. Complete.

I recommend trying these steps out on a test environment first.

• Proposed as answer by Dane1990 Monday, June 17, 2013 11:08 AM

Hi Zahir / All

I come access this issue when trying to migrate a Hyper V Virtual Machine from Windows Server 2008 R2 to Windows Server 2012 using SCVMM 2012. I spent a bit of time researching finding an easy way to get round it and finally just worked out a way myself by creating a new test machine, thought I would post the steps here;

1. Shut down the virtual machine you want to migrate.
2. In VMM 2012 > 'VM's and Services' Right click on the virtual machine, click properties.
3. Click "Hardware Configuration"
4. Scroll down to Network Adapters and choose, you network adapter.
5. Under connectivity, choose "Not Connected". Click ok.
6. You should then be able to migrate the virtual machine.
7. Once the migration is complete, go back into the Network Adapter properties.
8. Click "Connected to a VM network"
9. And choose a VM network available. I didn't worry about the VM Subnet section and just left it blank. Click ok
10. Turn on the virtual machine. Complete.

I recommend trying these steps out on a test environment first.

• Proposed as answer by Dane1990 Monday, June 17, 2013 11:08 AM

Hi Zahir / All

I come access this issue when trying to migrate a Hyper V Virtual Machine from Windows Server 2008 R2 to Windows Server 2012 using SCVMM 2012. I spent a bit of time researching finding an easy way to get round it and finally just worked out a way myself by creating a new test machine, thought I would post the steps here;

1. Shut down the virtual machine you want to migrate.
2. In VMM 2012 > 'VM's and Services' Right click on the virtual machine, click properties.
3. Click "Hardware Configuration"
4. Scroll down to Network Adapters and choose, you network adapter.
5. Under connectivity, choose "Not Connected". Click ok.
6. You should then be able to migrate the virtual machine.
7. Once the migration is complete, go back into the Network Adapter properties.
8. Click "Connected to a VM network"
9. And choose a VM network available. I didn't worry about the VM Subnet section and just left it blank. Click ok
10. Turn on the virtual machine. Complete.

I recommend trying these steps out on a test environment first.

• Proposed as answer by Dane1990 Monday, June 17, 2013 11:08 AM

Hi Dane1990,

Spot on answer for an exact scenario. I just told SCVMM to attach the correct network during the migration wizard.

Thanks once again!

Jay

Thanks,

This worked for me as i was having this issue trying to convert vmware to hyperv vm's but this resolves the issue.

This work exactly as you said. I was also able to add a network adapter to the new cluster network through the "Migrate Virtual Machine" wizard, bypassing steps 7-9. Both ways worked great for me, thanks for the answer Dane1990!

Unbelievable. I've been researching Logical Networks, Logical Switches, and VM Networks for three days with no answer to this until the Dane answer above. Some times things are so simple yet seem so hard. Just disconnect the virtual adapter and everything is great. Wow!

Using VMM 2012 R2.

Thanks for this. Bill

Wonderfully. Its Works . Just disconnect the network adapter and you can live migration without errors.

Many thanks.