VM's in Hyper V Manager doesnt start

We are also assuming that there is also enough disk space on your cluster.

You can check normally in Disk Manager for the disk space. However, you are maybe using CSV disks for your VMs within the cluster.

If this is the case (using CSV) follow these steps to check your free space:

1. Open the Failover Cluster Manager console
2. Expand your cluster name (on the left), expand Cluster Shared Volumes (CSV)
3. On the central view you will have a list of your different drives used as CSV, expand each one of them and check the free space within them.

Please publish the results in a TXT file from ALL nodes in the cluster:

Get-VMHost | fl VirtualHardDiskPath,VirtualMachinePath

Hi I only see Roles ,Nodes , Storage and Networks , When I look under storage there are still enough storage

Hi Philip , please send me example of how to run the powershell command

Get-VMHost | fl VirtualHardDiskPath,VirtualMachinePath | out-file c:\test\vms.txt

Select allOpen in new window

Hi David

Below is the output that I get in the .txt file


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

I see a lot of XML files under these folders

Tx

All of your node's VirtualHardDiskPath and VirtualMachinePath settings should be set to a CSV that is accessible by all nodes.

The CSV must have enough GB to hold:
1: Memory files of all VMs
2: configuration files
3: Snapshot files (we don't do this at all)

Our formula is:
=sum(RAM Node 1-5) + 150GB

For us, our first CSV is _always_ the location for the above. So, we set them to:
VirtualHardDiskPath : C:\ClusterStorage
VirtualMachinePath  : C:\ClusterStorage\Volume1

How available memory have your HyperV servers, and how much memory is required by your VM?


I made the question because the problem looks like to be related to disk or memory resources. If CSVs are not used, and there is enough disk space on your drives. We can also take a look to the memory resources. Be aware that all the free memory cannot be assigned to VMs as far as the OS reserves memory for the administrative tasks. Another important detail is related to your cluster failover scenarios, if one node fails how can the remaining servers to stay in service dividing the load of resources from the failed server.

Hi Philip , How do I set


 VirtualHardDiskPath : C:\ClusterStorage
 VirtualMachinePath  : C:\ClusterStorage\Volume1

Thanks for the response

and you've used the cluster manager to ensure that the cluster is healthy and has lots of disk space available?

On each node:
Set-VMHost -VirtualHardDiskPath “C:\ClusterStorage” –VirtualMachinePath “C:\ClusterStorage\Volume1”

Is this a lab cluster setup?

Very important question from Philip. Because using a CSV is a change for your cluster design and its way to work. However, CSV is better than failovers from the disk owner perspective because with CSV the disk is accessed at the same time by your nodes and transfers are performed much master.

However, it requires many things, such as assigning storage as CSV, moving your current VMs storage location to the CSV storage and changing the default parameters for saving the VMs.

Hi Everyone

This is within in my production environment , I wish it was in the lab : )

I do have 3 lun's on my san  volume 1 has 454GB of space Volume 2 256GB of space and Volume 3 has 900GB of space , so space is not the issue

So if Change the path On each node:
 Set-VMHost -VirtualHardDiskPath “C:\ClusterStorage” –VirtualMachinePath “C:\ClusterStorage\Volume1” should this fix my problem?

Hi Thanks I wil get someone to have a look