asked on

VMs on one host is failing for live migration

SetUp:

2 x Hyper-V 2012R2 Hosts
2 VMs on Host 1
2 VMs on Host 2
Clustered Storage Volume via iSCSI
Volume 1 is attached to Host 1
Volume 2 is attached to Host 2

Issues:

Unable to migrate VMs from Host 1 to Host 2
VMs from Host 2 can migrate to Host 1

Errors:

VM 1 from Host 1 throws a 21502 Error
VM 2 from Host 1 states "Clustered storage is not connected to the node

Cliff Galiher

Both volumes should be connected to both nodes. That's the point of a cluster SHARED volume (CSV) is that both nodes have access to the storage. My guess is volume 2 is indeed connected to both nodes so love migrations succeed, but volume 1 is not. Based on the bullet points in your description, you didn't intentionally configure the volumes to be shared.

Steven Hoong

ASKER

So I'm able to access both storage volumes in both nodes. When I go to the Failover Cluster Manager and go under nodes, I click on each node and check the disks tab and each CSV is mounted to each host.

Cliff Galiher

The errors would indicate that this isn't the case. I would check the cluster configuration and network health. Since iSCSI is built on TCP/IP, all of the network troubleshooting steps would apply. I'm guessing node 2 cannot consistently access volume 1 due to a misconfiguration or network issue.

Philip Elder

Please publish the results of the following from both nodes:

Get-VMHost | fl VirtualHardDiskPath,VirtualMachinePath

Open in new window

Steven Hoong

ASKER

Host 1:

VirtualHardDiskPath : C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks
VirtualMachinePath : C:\ProgramData\Microsoft\Windows\Hyper-V

Host 2:

VirtualHardDiskPath : D:\Hyper-V\Virtual Hard Disks
VirtualMachinePath : D:\Hyper-V

Cliff Galiher

Well, the default paths don't appear to be on a CSV. Maybe the individual VM paths are and were created overriding the defaults.... But I suspect not, again based on the errors.

SOLUTION

Philip Elder

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Steven Hoong

ASKER

So when I log into the host, I see the CSV and when I drill into the path, I see the respective VHDX for each VM listed

ASKER CERTIFIED SOLUTION

Philip Elder

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Steven Hoong

ASKER

so for host 1 vm1, the file is not. for host 1 vm2, it is.

is there a powershell command i can run against the vm to see where the xml file is located?

Steven Hoong

ASKER

so after digging around a bit, all VMs have their configuration files on their respective local hosts (C:\ProgramData\Microsoft\Windows\Hyper-V)

Steven Hoong

ASKER

So I checked the location of all files under the Failover Cluster Manager and found that the files on Host 1 was all over the place. After i mirrored the locations respectively to the working VMs I'm able to migrate everything back and forth! Thanks again!

Philip Elder

You can use the Storage Live Migration feature in Failover Cluster Manager or Hyper-V Manager to move the configuration files to the correct CSV location. That's the simplest way to do so.