06.08
Microsoft has moved the location of where you configure the LM network with the release candidate of Windows Server 2012 Hyper-V. The old location was confusing … right-click on the properties of a single Virtual Machine resource (in the VM group), and that applied to all VMs. As a speaker, the bewildered and confused look on people’s faces at that point was always worrying.
And thankfully, it is now relocated to somewhere more obvious, and clear that it’s a cluster wide setting:
- Right-click on Networks
- Select Live Migration Settings
In this new dialog box, you can order the networks (from the above Networks node in Failover Cluster Manager), and select which ones are to be used for Live Migration. I like to make my network names clear, so it’s obvious what is what here.
Copyright Warning
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.
Related posts:
- Passthrough Disks –ARE– Still Supported By WS2012 Hyper-V Live Migration, But With Limits
- KB2779204 – Live Migration Of Or Starting WS2012 Hyper-V VMs Fails With 0×80070569 Error
- Live Migration Security Failures, Kerberos Live Migration Authentication & Constrained Delegation
- How To Move Highly Available VMs to a WS2012 Hyper-V Cluster
So which one of those networks do you run your CSV traffic over?
BTW – I’m really enjoying all your posts on the new Stuff in Hyper-V – excellent stuff and really interesting :-)
Thanks – the cluster network.
Anyone else getting an error when trying this from a windows 8 desktop. Works from the server though.
Was always a strange way of doing it in W2K8R2.. now much simpler..
Any equivalent way to do the same thing, on a 2012 Cluster, for HA VMs, using Powershell?
Sadly, no, not that I’ve been able to find, and the cluster team have not been able to give me an answer to that one either. There might be a hack for doing it using PowerShell via WMI.