Microsoft has published the release notes for System Center 2012 R2 – Virtual Machine Manager (VMM). There are some important notes there, but I thought I’d highlight a few that stick out:
- For file server clusters that were not created by VMM, deploying the VMM agent to file server nodes will enable Multipath I/O (MPIO) and claim devices. This operation will cause the server to restart. Deploying the VMM agent to all nodes in a Scale-out File Server cluster will cause all nodes to restart.
- Generation 2 virtual machines are not supported
- If System Center 2012 R2 VMM is installed on Windows Server 2012, you cannot manage Spaces storage devices that are attached to a Scale-out File server. Spaces storage requires an updated SMAPI that is included with Windows Server 2012 R2 release version.
- The Physical-to-Virtual (P2V) feature will be removed from the System Center 2012 R2 release.
- Windows Server supports storage tiering with Storage Spaces. However, VMM does not manage tiering policy.
- Windows Server supports specifying write-back cache amount with Storage Spaces. However, VMM does not manage this.
- Performing a Hyper-V Replica failover followed by a cluster migration causes the VMRefresher service to update the wrong virtual manager, putting the virtual machines into an inconsistent state.
- VMM does not provide centralized management of World Wide Name (WWM) pools.
- Failing over and migrating a replicated virtual machine on a cluster node might result in an unstable configuration
And there’s more. Some have workarounds (see the original article). Some do not, e.g. removal of P2V from VMM 2012 R2 or lack of support for G2 VMs. In those cases:
- Use 3rd party tools or DISK2VHD (no DISK2VHDX tool) for P2V
- Continue to use G1 VMs if using VMM. Remember that there is no conversion between G1 and G2