I have a (2) node cluster setup using Windows 2008 R2 x64 Enterprise.
This cluster is setup with (2) NICs on each server, (1) NIC dedicated to production traffic (10.0.1.0/24), and (1) NIC dedicated to SAN traffic (172.16.20.0/24).
The SAN has (1) 500GB LUN setup for VM storage (VHDs, configs, etc...), and (1) 10GB LUN setup for Quorum.
Before cluster setup, Hyper-V role was added to each Windows 2008 R2 server and verified as working. Hyper-V Virtual networks were also configured on each server using the default configuration and pinning that configuration to the PRODUCTION NIC and not to the SAN NIC.
The cluster passes verification and is setup as a simple cluster. No services are added, and shared cluster storage is enabled (new feature for Hyper-V R2). The clusters VMs will be stored here.
Hyper-V is made highly available using the failover cluster admin, and both nodes recognize each other. The cluster converges fine, and communicates well.
After all of this was setup, we imported a VM into the Hyper-V R2 server, and made sure that it worked correctly. We then began testing LIVE MIGRATIONS, which would fail instantly with:
'Virtual Machine SERVER' live migration did not succeed at the destination.
Configuration setup for live migration failed on the destination node. Make sure that name of the virtual network is the same on the source and destination nodes, and try the live migration again
and
Virtual Machine Configuration SERVER' failed to create the virtual network switch ports for the virtual machine. Check the settings of the virtual machine.
Followed by error code 32, details are:
________________________________________
Failed to connect NIC '1CC9594D-0902-4C68-9928-17A852007737--0' to port '' on switch 'SWITCH-SM-5E878167-0C71-46FB-A869-A5294BC2377', status = C000003A.
After we try to do a QUICK MIGRATION, the other cluster node DOES pick up ownership of the Hyper-V VM, but when the other node attempts to start the VM we get the following error (again, 21502):
________________________________________
'Virtual Machine SERVER' failed to start.
'SERVER' failed to restore. (Virtual machine ID 1CC9594D-0902-4C68-9928-17A852007737)
'SERVER' Microsoft Emulated Ethernet Port (Instance ID {718032DA-6EFB-4EF4-8152-9A2FBDA945BF}): Failed to restore with Error 'The system cannot find the path specified.' (0x80070003). (Virtual machine ID 1CC9594D-0902-4C68-9928-17A852007737)
'SERVER' The switch port connection for "Ethernet Port" (1CC9594D-0902-4C68-9928-17A852007737--0) is unsupported.
Any help would be appreciated as this is preventing LIVE MIGRATION and FAILOVER CLUSTERING on what appears to be a perfectly functioning Cluster.
by: plimpiasPosted on 2009-09-12 at 12:19:01ID: 25317549
The named of the virtual network adapters must be the same, I think this may be your problem