Hyper V Lab and Live Migration

Hi Guys,
I have 2 Hyper V hosts I am setting up in a lab environment. Initially, I successfully setup a 2 node cluster with CSVs which allowed me to do Live Migrations.
The problem I have is my shared storage is a bit of a cheat as I have one disk assigned in each host and each host has starwinds virtual SAN installed. The hostA has an iscsi connection to hostB storage and visa versa.
The issue this causes is when the hosts shutdown (because this is a lab its only on when required), the cluster is in a mess when it starts up eg VMs missing etc. I can recover from it but it takes time. I tinkered with the HA settings and the VM settings
so they restarted/ didnt restart etc but with no success.
My question is can I use something like SMB3 shared storage on one of the hosts to perform live migrations but without a full on cluster? I know I can do Shared Nothing Live Migrations but this takes time.
Any ideas on a better solution (rather than actually buying proper shared storage ;-) ) Or if shared storage is the only option to do this cleanly, what would people recommend bearing in mind I have SSDs in the hyper V hosts.
Hope all that makes sense

Hi Sir,
>>I have 2 Hyper V hosts I am setting up in a lab environment. Initially, I successfully setup a 2 node cluster with CSVs which allowed me to do Live Migrations.
As you mentioned , you have 2 hyper-v host and use starwind to provide ISCSI target (this is same as my first lab environment ) , then I realized that I need one or more host to simulate more production scenario .
But ,if you have more physical computers you may try other's progects .
Also please refer to this thread :
https://social.technet.microsoft.com/Forums/windowsserver/en-US/e9f81a9e-0d50-4bca-a24d-608a4cce20e8/2012-r2-hyperv-cluster-smb-30-sofs-share-permissions-issues?forum=winserverhyperv
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

When setting up converged network in VMM cluster and live migration virtual nics not working

Hello Everyone,
I am having issues setting up converged network in VMM. I have been working with MS engineers to no avail. I am very surprised with the expertise of the MS engineers. They had no idea what a converged network even was. I had way more
experience then these guys and they said there was no escalation track so I am posting here in hopes of getting some assistance.
Everyone including our consultants says my setup is correct.
What I want to do:
I have servers with 5 nics and want to use 3 of the nics for a team and then configure cluster, live migration and host management as virtual network adapters. I have created all my logical networks, port profile with the uplink defined as team and
networks selected. Created logical switch and associated portprofle. When I deploy logical switch and create virtual network adapters the logical switch works for VMs and my management nic works as well. Problem is that the cluster and live
migration virtual nics do not work. The correct Vlans get pulled in for the corresponding networks and If I run get-vmnetworkadaptervlan it shows cluster and live migration in vlans 14 and 15 which is correct. However nics do not work at all.
I finally decided to do this via the host in powershell and everything works fine which means this is definitely an issue with VMM. I then imported host into VMM again but now I cannot use any of the objects I created and VMM and have to use standard
switch.
I am really losing faith in VMM fast.
Hosts are 2012 R2 and VMM is 2012 R2 all fresh builds with latest drivers
Thanks

Have you checked our whitepaper http://gallery.technet.microsoft.com/Hybrid-Cloud-with-NVGRE-aa6e1e9a for how to configure this through VMM?
Are you using static IP address assignment for those vNICs?
Are you sure your are teaming the correct physical adapters where the VLANs are trunked through the connected ports?
Note; if you create the teaming configuration outside of VMM, and then import the hosts to VMM, then VMM will not recognize the configuration.
The details should be all in this whitepaper.
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

2012 R2 Cluster and Live Migration

6 Node Cluster with Server 2012 R2, all VM's are Server 2012 R2
4 Fiber SAN's
Moving and Live Migration worked fine in FailOver Cluster Manager
But this time we were trying do it with SCVMM 2012 R2 and just move one VM (Gen2)
Of course it failed at 99%
Error (12711)
VMM cannot complete the WMI operation on the server (whatever) because of an error: [MSCluster_Resource.Name="SCVMM VMHost"] The cluster resource could not be found.
The cluster resource could not be found (0x138F)
Recommended Action
Resolve the issue and then try the operation again.
How do I fix this? the VM is still running. The two vhdx files it was moving are smaller then orginal's , but it change the configuration file to point to new ones, which are bad.
it says I can Repair it... Redo or Undo....of course neither of those options work.
Wait for the object to be updated automatically by the next periodic Live migrate storage of virtual machine vmhost from whatever to whatever job.
ID: 1708
Cluster has no errors, SAN's have no errors, CSV have no errors. the machine running scvmm is VM running on the cluster

How did you create this VM? if this is created outside of VMM, I recommend doing a manual refresh of the VM first to ensure that VMM can read its attributes. Then retry the operation.
Btw, are the VMs using diff disk? any checkpoints associated with them?
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

Hyper-v 2012 R2 Live migration issue in 2003 Domain function Level

hi Team ,
i recently build 2012 R2 Hyper-v Cluster with three node. Everrything working fine with out any issue . Cluster working also fine. Later i came across one issue when tried to Live migration virtual machine from one host to another . it failed all the time
while quick migration is working . i gone through few articles and find it is known issue with hyper-v 2012 R2 where domain functional level is set to 2003 . although they have provided Hotfix but no solution.
http://support.microsoft.com/kb/2838043
Please let me know if any one face similar issue and able to resolve by any hotfix. My host are updated .
Thanks
Ravindra
Ravi

Hi Ravi1987,
The KB2838043 is applied for Server 2012 node, Could you offer us the related cluster error event id, or you can refer the following article to check your cluster
network binding order is correct or not.
Configuring Windows Failover Cluster Networks
http://blogs.technet.com/b/askcore/archive/2014/02/20/configuring-windows-failover-cluster-networks.aspx
You can try to install recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters first, then monitor this issue again.
The KB download:
Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
http://support.microsoft.com/kb/2920151
More information:
Windows Server 2008 R2 Live Migration – “The devil may be in the networking details.”
http://blogs.technet.com/b/askcore/archive/2009/12/10/windows-server-2008-r2-live-migration-the-devil-may-be-in-the-networking-details.aspx
I’m glad to be of help to you!

Hyper-V Failover Cluster Live migration over Virtual Adapter

Hello,
Currently we have a test environment 3 HyperHost wich have 2 Nic teams. LAN team and team Live/Mngt.
In Hyper-V we created a Virtual Switch (Wich is Nic team Live/Mngt)
We want to seperate the Mngt and live with Vlans. To do this we created 2 virtual adapters. Mngt and Live, assigned ip adresses and 2 vlans(Mngt 10, Live 20)
Now here is our problem: In Failover cluster you cannot select the Virtual Adapter(live). Only the Virtual Switch wich both are on. Meaning live migration simple uses the vSwitch instead of the Virtual adapter.
Either its not possible to seperate Live migration with a Vlan this way or maybe there are Powershell commands to add Live migration to a Virtual adapter?
Greetings Selmer

It can be done in PowerShell but it's not intuitive.
In Failover Cluster Manager, right-click Networks and you'll find this:
Click Live Migration Settings and you'll find this:
Checked networks are allowed to carry traffic. Networks higher in the list are preferred.
Eric Siron
Altaro Hyper-V Blog
I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.

Hyper-V 2012 R2 - live migration dynamic memory issue

Hi..
we use a two node hyper-v cluster.
On each node running 5 vm that shared the 64GB system memory.
The vms are configured to use dynamic memory. The sum of the startup (min) memory of the 10 vms are currently 50 GB.
So now our problem:
If we try to drain roles on node A for maintenance purpose two vms are still on node A because they wasted currently each 25GB memory and so on node B is not enough free memory to host this vms.
That sounds logical
But as all vms configured to use dynamic memory they should shrink their memory to get enough space for all vms? If we shutdown all vms, move it to one node, then everything works fine.
Is it by design that live migration do not trigger the vm to shrink their memory?
Best regards, Alexander Zirbes

Hi Alexander,
Dynamic memory means that memory can increase or decrease based on the demand of the VM, not based on the load of the Hyper-V host. If the gust OS of VM dont need that much memory, memory will be released. I dont think live migration has any role shrinking
the allocated memory of a VM.
Since you are using two node cluster, you should only load 50% resourses on each host so that incase of a failure of second node, the first node can have all the VMs.
This calculation will become more effective if you have more nodes. I am having a six node cluster and I load each host upto 80% so that in case of a single node failure, the VMs can be split on other five nodes without issues.
Cheers,
Shaba
Optimism is the faith that leads to achievement. Nothing can be done without hope and confidence.
InsideVirtualization.com

Oracle VM (XEN) and Live Migration throws PCI error

First off, anyone using a HS21 XM blade with Oracle VM? Anyone attempted a live-migration, does it work?
When attempting a live migration on a HS21 XM blade we get the following errors and the host hangs:
102 I Blade_02 08/10/08, 08:46:38 (CADCOVMA02) Blade reboot
103 E Blade_02 08/10/08, 08:46:26 (CADCOVMA02) Software critical interrupt.
104 E Blade_02 08/10/08, 08:46:21 (CADCOVMA02) SMI Hdlr: 00150700 PERR: Slave signaled parity error B/D/F/Slot=07000300 Vend=8086 Dev=3 0C Status=8000
105 E Blade_02 08/10/08, 08:46:19 (CADCOVMA02) SMI Hdlr: 00150900 SERR/PERR Detected on PCI bus
106 E Blade_02 08/10/08, 08:46:19 (CADCOVMA02) SMI Hdlr: 00150700 PERR: Slave signaled parity error B/D/F/Slot=00020000 Vend=8086 Dev=25F7 Statu
107 E Blade_02 08/10/08, 08:46:18 (CADCOVMA02) PCI PERR: parity error.
108 E Blade_02 08/10/08, 08:46:17 (CADCOVMA02) SMI Hdlr: 00150900 SERR/PERR Detected on PCI bus
109 E Blade_02 08/10/08, 08:46:17 (CADCOVMA02) SMI Hdlr: 00150400 SERR: Device Signaled SERR B/D/F/Slot=07000300 Vend=8086 Dev=350C Sta us=4110
110 E Blade_02 08/10/08, 08:46:16 (CADCOVMA02) SMI Hdlr: 00150400 SERR: Device Signaled SERR B/D/F/Slot=00020000 Vend=8086 Dev=25F7 Status=4110
111 E Blade_02 08/10/08, 08:46:14 (CADCOVMA02) PCI system error.
any ideas? I've called IBM support but their options are reseat the hardware or replace it. this happens on more than one blade so we're assuming it has something to do with oracle VM. Thanks!

Hi Eduardo,
How are things going ?
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Best Configuration for T4-4 and live migration

I have several T4-4 servers with Solaris 11.1
What kind of settings I need for production environments with OVM live migration?
Should I use OVM manager for rugged environments?
Should I set two io-domain on each server?
Considering that I do live migration, for guess ldom system disk should I configure (publish) one big LUN to all servers or just a separate LUN for each ldom guest.

For the first questions: it's best to have separate LUNs or other backend disks for each guest - otherwise how would you plan to share them across different guests and systems? Separate LUNs also is good for performance by encouraging parallel I/O. Choice of using an additional I/O domain is up to you, but it's very typical for production users because of the resiliency it adds.
For advice on live migration, seehttps://blogs.oracle.com/jsavit/entry/best_practices_live_migration
Other blog posts after that discuss availability and performance.
Hope that helps, Jeff

LDOMs, Solaris zones and Live Migration

Hi all,
If you are planning to use Solaris zones inside a LDOM and using an external zpool as Solaris zone disk, wouldn't this break one of the requirements for being able to do a Live Migration ? If so, do you have any ideas on how to use Solaris zones inside an LDOM and at the same time be able to do a Live Migration or is it impossible ? I know this may sound as a bad idea but I would very much like to know if it is doable.

Thanks,
By external pool I am thinking of the way you probably are doing it, separate LUNs mirrored in a zpool for the zones coming from two separate IO/Service domains. So even if this zpool exist inside the LDOM as zone storage this will not prevent LM ? That's good news. The requirement "no zpool if Live Migration" must then only be valid for the LDOM storage itself and not for storage attached to the running LDOM. I am also worried about a possible performance penalty introducing an extra layer of virtualisation. Have you done any tests regarding this ?

Hyper-V host crash and live migration - what happens?

Hello there,
it would be great if you could help me understand how live migrationworks on a sudden host crash of a cluster node.
I know that the cluster functionality mounts the vhd file on another host and runs the VM.
But what happens to the VM itself? Does it crash too and is simply restarted on another host?
To my knowledge the RAM of the VM is run in the RAM of the host, wo I would assume that is all lost on a host crash?
Thanks for any help understanding this,
Best regards, Marcus

In a sudden crash, there is no time for the state of any running VMs to move to another system. Therefore, the VM is restarted on another node of the cluster. Think of the host crashing as being the same as pulling the power cable on the VM.
. : | : . : | : . tim

Live Migration failed using virtual HBA's and Guest Clustering

Hi,
We have a Guest Cluster Configuration on top of an Hyper-V Cluster. We are using Windows 2012 and Fiber Channel shared storage.
The problem is regarding Live Migration. Some times when we move a virtual machine from node A to node B everything goes well but when we try to move back to node A Live Migration fails. What we can see is that when we move the VM from node A to B and Live
Migration completes successfully the virtual ports remain active on node A, so when we try to move back from B to A Live Migration fails because the virtual ports are already there.
This doesn't happen every time.
We have checked the zoning between Host Cluster Hyper-V and the SAN, the mapping between physical HBA's and the vSAN's on the Hyper-V and everything is ok.
Our doubt is, what is the best practice for zoning the vHBA on the VM's and our Fabric? We setup our zoning using an alias for the vHBA 1 and the two WWN (A and B) on the same object and an alias for the vHBA 2 and the correspondent WWN (A and B). Is it
better to create an alias for vHBA 1 -> A (with WWN A) and other alias for vHBA 1 -> B (with WWN B)?
The guest cluster VM's have 98GB of RAM each. Could it be a time out issue when Live Migration happen's and the virtual ports remain active on the source node? When everything goes well, the VM moves from node A with vHBA WWN A to node B and stays there
with vHBA WWN B. On the source node the virtual ports should be removed automatically when the Live Migration completes. And that is the issue... sometimes the virtual ports (WWN A) stay active on the source node and when we try to move back the VM Live Migration
fails.
I hope You may understand the issue.
Regards,
Carlos Monteiro.

Hi ,
Hope the following link may help.
To support live migration of virtual machines across Hyper-V hosts while maintaining Fibre Channel connectivity, two WWNs are configured for each virtual Fibre Channel adapter: Set A and Set B. Hyper-V automatically alternates between the Set A and Set B
WWN addresses during a live migration. This ensures that all LUNs are available on the destination host before the migration and that no downtime occurs during the migration.
Hyper-V Virtual Fibre Channel Overview
http://technet.microsoft.com/en-us/library/hh831413.aspx
More information:
Hyper-V Virtual Fibre Channel Troubleshooting Guide
http://social.technet.microsoft.com/wiki/contents/articles/18698.hyper-v-virtual-fibre-channel-troubleshooting-guide.aspx
Hyper-V Virtual Fibre Channel Design Guide
http://blogs.technet.com/b/privatecloud/archive/2013/07/23/hyper-v-virtual-fibre-channel-design-guide.aspx
Hyper-V virtual SAN
http://salworx.blogspot.co.uk/
Thanks.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Server 2012 cluster - virtual machine live migration does not work

Hi,
We have a hyper-v cluster with two nodes running Windows Server 2012. All the configurations are identical.
When I try to make a Live migration from one node to the other I get an error message saying:
Live migration of 'Virtual Machine XXXXXX' failed.
I get no other error messages, not even in event viewer. This same happens with all of our virtual machines.
A normal Quick migration works just fine for all of the virtual machines, so network configuration should not be an issue.
The above error message does not provide much information.

Hi,
Please check whether your configuration meet live migration requirement:
Two (or more) servers running Hyper-V that:
Support hardware virtualization.
Yes they support virtualization.
Are using processors from the same manufacturer (for example, all AMD or all Intel).
Both Servers are identical and brand new Fujitsu-Siemens RX300S7 with the same kind of processor (Xeon E5-2620).
Belong to either the same Active Directory domain, or to domains that trust each other.
Both nodes are in the same domain.
Virtual machines must be configured to use virtual hard disks or virtual Fibre Channel disks (no physical disks).
All of the vitual machines have virtual hard disks.
Use of a private network is recommended for live migration network traffic.
Have tried this, but does not help.
Requirements for live migration in a cluster:
Windows Failover Clustering is enabled and configured.
Yes
Cluster Shared Volume (CSV) storage in the cluster is enabled.
Yes
Requirements for live migration using shared storage:
All files that comprise a virtual machine (for example, virtual hard disks, snapshots, and configuration) are stored on an SMB share. They are all on the same CSV
Permissions on the SMB share have been configured to grant access to the computer accounts of all servers running Hyper-V.
Requirements for live migration with no shared infrastructure:
No extra requirements exist.
Also please refer to this article to check whether you have finished all preparation works for live migration:
Virtual Machine Live Migration Overview
http://technet.microsoft.com/en-us/library/hh831435.aspx
Hyper-V: Using Live Migration with Cluster Shared Volumes in Windows Server 2008 R2
http://technet.microsoft.com/en-us/library/dd446679(v=WS.10).aspx
Configure and Use Live Migration on Non-clustered Virtual Machines
http://technet.microsoft.com/en-us/library/jj134199.aspx
Hope this helps!
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Lawrence
TechNet Community Support
I have also read all of the technet articles but can't find anything that could help.

Host server live migration causing Guest Cluster node goes down

Hi
I have two node Hyper host cluster , Im using converged network for Host management,Live migartion and cluster network. And Separate NICs for ISCSI multi-pathing. When I live migrate the Guest node from one host to another , within guest cluster the node
is going down. I have increased clusterthroshold and clusterdelay values. Guest nodes are connecting to ISCSI network directly from ISCSI initiator on Server 2012.
The converged networks for management ,cluster and live migration networks are built on top of a NIC Team with switch Independent mode and load balancing as Hyper V port.
I have VMQ enabled on Converged fabric and jumbo frames enabled on ISCSI.
Can Anyone guess why would live migration cause failure on the guest node.
thanks
mumtaz

Repost here: http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/threads
in the Hyper-V forum. You'll get a lot more help there.
This forum is for Virtual Server 2005.

Live migration Vnic on hosts randomly losing connectivity HELP

Hello Everyone,
I am building out a new 2012 R2 cluster using VMM with converged network configuration. I have 5 physical nics and teaming 3 of them using dynamic load balancing. I have configured 3 virtual network adapters in host which are for management,
cluster and Live migration. The live migration nic loses connectivity randomly and fails migrations 50% of the time.
Hardware is IBM blades (HS22) with Broadcom Netextreme II nics. I have updated firmware and drivers to the latest versions. I found a forum with something that looks very similar but this was back in November so Im guessing there is a fix.
http://www.hyper-v.nu/archives/mvaneijk/2013/11/vnics-and-vms-loose-connectivity-at-random-on-windows-server-2012-r2/
Really need help with this.
Thanks

Hi,
Does your cluster can pass the cluster validation test? Please install the recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters update first
then monitor again.
More information:
Configuring Windows Failover Cluster Networks
http://blogs.technet.com/b/askcore/archive/2014/02/20/configuring-windows-failover-cluster-networks.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Cannot perform a live migration while replication is enabled

I have two Server 2012 machines that I am running hyper-v on (just testing for now). I can right click on a virtual machine and move it (live migration) to the other server with no issues. I can also enable replication on the VM and that
appears to work properly. However, if I have replication enabled on a VM I am unable to perform a live migration. I receive an error that says the VM already exists on the destination server (because of the replication).
Is there any way to perform a live migration while replication is enabled?

I can't think of a reason why you would want to anywhere else but a test environment. Replication's intended use is DR across a WAN between two physical location (there are others, but this is primarily why it was created). If Office1 burns down, you can
boot your Replica at Office2. Live Migration is for local HA. If Server1 has a hardware failure, Live Migrate to Server2.
If everyone could simply Live Migrate over their WAN link between offices, Replication would be redundant. But getting a fast enough WAN link for this is extremely expensive, so Microsoft created Replication for high latency, low bandwidth WAN connections.
TL;DR, Replication and Live Migration are mutually exclusive in almost all environments. It's not even that they *can't* work together, it's just that there's no point in making them work together because they're for different use cases.

Hyper V Lab and Live Migration

Similar Messages

Maybe you are looking for