Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have two w2k8r2 machines, that are in cluster, There are also two machines that are used as shared storage (with StarWind installed). On each node of the cluster there is one VM. So tell me please is it possible to cross-live=migrate VMs? Other words can I perform Live Migration of each VM, that are on different cluster nodes, simultaneously?

Thak you very much for now.

share|improve this question

can't see why not - this works with kvm, why not with hyper-v?

share|improve this answer
can with ESX(i) too – Chopper3 Oct 27 '10 at 15:00
I dont know why - I'm startin LM of first machine, then second, and getting error on the second one (event ID 1205). Has anyone actually tried this? @Chopper3 - I had success with ESX too. – user57037 Oct 27 '10 at 15:09
I guess you might want to check the migration related logs, to see what exactly fails – dyasny Oct 27 '10 at 15:15
That error suggest you're losing iSCSI connectivity, are you using that for quorum/msdtc? – Chopper3 Oct 27 '10 at 16:20
can you migrate one VM, make sure it finishes migrating, and then start the migration of the second one? I do suspect hyper-v has a limitation of a single migration at a time – dyasny Oct 27 '10 at 16:25

If your trying Hyper-V Live Migration with iSCSI there are some setup requirements that I'm not remembering off the top of my head that you need to do with iSCSI Initiator and storage to make sure the LUN can hop to the other server. Normally targets are initiator specific, and with different SAN software you perform the steps differently to support clustering of the LUN/volume.

I would think your storage vender would have documentation on the clustered storage part, and Hyper-V Live Migration would have documentation on the things to check to ensure the LUN "hops" from one server to another.

I also remember in 2008 R2 clustered shared volumes (many nodes write to one volume) is a good thing, allowing you to store all VM's on one LUN rather than their own.

Yes I've seen migrations simultaneously in opposite directions, it may have been Quick Migration though.

Lastly the big no no is to have the host NIC and the iSCSI NIC be the same one. Really in your scenario you want at least three, one dedicated to host, one dedicated to guest network access, and one dedicated to iSCSI on host. Microsoft actually recommends 4, with the 4th dedicated to Live Migration.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.