Hi,
I have VMM 2012 SP1 (Update rollup 1 installed). In VMM, we have:
- A logical network defined with sites that are using private VLANs (3 sites defined with same primary VLAN and different private VLANs)
- Each site has an address pool and VM Network defined for it
- Cluster with 2 Win2012 hosts
- Each cluster host has 2 NICs in a team created by VMM using the same Logical Switch. Each NIC has the same port profile. Hardware details for host show all applicable sites.
- All logical switches are Compliiant, all hosts are Fully Compliant in the logical switch view.
- Cluster passes validation. All warnings are unrelated to the network.
I am able to create a VM using one of the PVLAN VM Networks without issue, VM is able to communicate fine. If I try to do a migration (with VM running or stopped), I get Error 26859:
------------------------------
Error (26859)
No matching Virtual Switch found on target host for Virtual network adapter VM Network (PV505) and port classification (High bandwidth).
Recommended Action
Select a different VM network and or port classification for the virtual network adapter
-------------------------------
The target (and source) host indeed has PV505 listed as available. "High Bandwidth" classification is the only one available on that virtual switch.
When I go through the migration wizard, the target host appears with a valid rating and no issues are reported. Migration job fails at 26% consistently. No migration attempt is visible in the Failover Cluster manager.
I *Am* able to live-migrate the VM via failover cluster without issue, and the VM is able to communicate after the migration.
If I remove the classification from the port, I get the same error except that the port classification is blank in the error.
If I move the VM to the other host via failover cluster, refresh so VMM see it there, I am not able to migrate the VM back to the original host.
In VMM settings, I have "Logical Network matching" set to "Virtual Network Switch Name", "Network Connection Name". The host does not have access to that VM Switch, so I can't use DNS names for that. Setting this setting to 'Disabled' does not have any effect on the migration failure.
If I shutdown the VM, remove it's NIC, then I can migrate it to the other host and re-add the NIC to the same VM network and boot the VM. I communicates without issue.
VMM server has been rebooted.
All help is appreciated as this is a bit of a shot stopper for using VMM. Thanks!
Alex