Hyper-V Failover Live Migration failed. Error 21502
-
@Dashrender
here is the mountvol.exe result.
-
awww - I think I see the problem.
Your volume on Disk 3 is set to 1 GB, not one TB. You only have 888 Megs free on that volume, and you need 2 GB (2048 MB) free for the RAM disk.
though I'm not sure how you installed Windows into a 1 GB partition.
-
Can you do a details based listing of what is is c:\clusterstorage\volume1?
-
@Dashrender
From your previous message currently I am redoing the whole iscsi and volume clustering. I will report back if the problem resolved. -
@LAH3385 said:
@Dashrender
The cluster storage space is configured with starWind vSAN. I gave it a good 1TB (1,0001GB)
What I can't tell, is this graphic showing 1.001 GB or 1,001 GB?
Assuming it's showing 1,001 GB (nearly 1 TB of space), this is only showing the whole array, not the the partitions that you created in the array.
-
@Dashrender said:
@LAH3385 said:
@Dashrender
The cluster storage space is configured with starWind vSAN. I gave it a good 1TB (1,0001GB)
We all missed what this graphic is actually showing - it shows that your Cluster Volume is only 1 GB, not 1 TB.
Yep. Comma or period is a big difference all right!
-
LOL!!!! I am pretty sure it is a comma
-
@travisdh1 said:
@Dashrender said:
@LAH3385 said:
@Dashrender
The cluster storage space is configured with starWind vSAN. I gave it a good 1TB (1,0001GB)
We all missed what this graphic is actually showing - it shows that your Cluster Volume is only 1 GB, not 1 TB.
Yep. Comma or period is a big difference all right!
Drat, you quoted me before I corrected my post - please see correction.
-
@LAH3385 said:
LOL!!!! I am pretty sure it is a comma
Yeah, so the Cluster Volume is fine, it's the partition on the cluster that's to small.
-
@Dashrender
Actually you were right! Not with the comma part, but the problem is I gave it 1TB size but linked it to 1GB partition. I didn't show the resource down belong it it only show 883MB out of 1GBNow it pointed to 1TB partition so it is working now.
-
Yeah, when MS stopped showing a real size comparison of partitions vs the whole volume, it became even more important to full read the stats, not just trust the graphic. If the graphic would have shown this tiny slice it would have been obvious that the slice was to small to use.
-
So considering that.. where was your VM actually sitting? How large is/was your VM?
-
@Dashrender
currently 125GB (starting size) on Disk 3 of 1TB. -
You were trying to do live migrations before - and it seemed like you had at least limited success - I'm wondering where the VM files where and how that happened?
-
@Dashrender
previously it failed because of Kerboros credential. After giving it delegate rights the live migration works. -
@LAH3385 said:
@Dashrender
previously it failed because of Kerboros credential. After giving it delegate rights the live migration works.even though the storage space was to small?
-
@Dashrender
yes. but previously I set it with 512MB which fit into the 1GB storage -
@LAH3385 said:
@Dashrender
yes. but previously I set it with 512MB which fit into the 1GB storageI'm confused - you set what to 512 MB? The PageFile for the VM? so the VM itself doesn't have to be on the shared storage?
-
@Dashrender
I am really new to the whole Hyper-V stuff so I don't really understand what you are implying.The 512MB is the RAM memory. I do not understand how is that matter at all but it seem it matter. I might be on the wrong universe here but somehow it is working and I am happy.
-
I'm just trying to understand how it works.
I would assume to get HA with Solarwinds you'd have to have the VM itself on the Clustered Shared Storage (CSS). But your CSS was only 1 GB, significantly smaller than the size of your VM (Assuming a 40 GB Windows VM).
You were doing a live migration that was giving you some sort of sorta success. I wonder if this was because you were doing a share nothing live migration, and not a real failover migration. By real failover I mean - a host died and the VM just kept on running on the other server. But maybe you weren't going for that kind of test.
Then after that you had the error talking about not having enough space (Event ID 21502 - it needed 2 GB and your storage was only 1 GB), so I'm really confused what was happening there. Since your VM could never have been running inside the CSS at 2 GB, why was the system even looking at the drive?
These are just thinking questions - ones that we probably won't get answers to.
