Hyper-V Cluster Storage

Hello,

I am new to Hyper-V Clustering.  I was attempting to create a new VM through Hyper-V Manager on one of our nodes in a cluster.  This is running on a Server 08 platform.  I downloaded Server 2012 and attempted to install it while creating this new VM.  I allocated 4 GBs of RAM and 100 GBs of storage for the VM.  At the 39% mark during the installation, the install hung and I got a prompt that the C drive space on the node was at a critical low status.  I checked and the free space on the C drive of the node is at 87 MBs.  I killed the installation of the VM, but the node is still at the 87 MB mark?  Does anyone have any suggestions on how to expand the drive on this or something?

Thanks
cheesebugahAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

cheesebugahAuthor Commented:
I noticed there is a 4 GB .bin file in this location, C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines.  There is a what looks like a registry older in there with the .bin file in it.  I was wondering if I could delete it as it was created at the time of the botched VM install, just to get some free space back?
arnoldCommented:
Not sure whether this is your testing platform, it is important when setting up hyper-v to make sure the locations that hyper-v will use for the guests. To avoid a situation such as this that the host's c drive is filled up.

What else is running on this Hyper-v host.  Look at the configuration of this VM and other VMs to see whether it is the sole VM that refers to the location in question while the others do not.
cheesebugahAuthor Commented:
There is another VM on this host that has its VHD pointing to a different location than the one I attempted to create.  The one I attempted to create is pointing to the C drive of the host.  It is the only one pointing to this location.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

arnoldCommented:
In this case the option is up to you to delete this VM and create a new one paying attention to where the vm config file and where it's disks are stored.
Double check that the Von that you will delete is referencing the earlier mentioned file onC: drive.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cheesebugahAuthor Commented:
Arnold,

I was able to "Remove" the VHD after shutting down the botched VM.  I now have available space on the C drive.  You pointed me in the right direction on this one.  I thank you.  I will pay closer attention to the VHD location next time during the install.
cheesebugahAuthor Commented:
Was able to go in and delete the VHD file associated with the new VM.  I suggest researching the location of other VM's VHD file location before just going through the prompts accepting the defaults.  My bad.
David Johnson, CD, MVPOwnerCommented:
if you go into the hyper-v settings you can change the default Virtual Machine  and Virtual hard Disk LocationsHyper-V Defaults
cheesebugahAuthor Commented:
Thank you David.  I guess I was awarding points while you were posting.  You have provided valuable information and it is greatly appreciated.
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
If this is a cluster setting is the clustered storage in Cluster Shared Volumes? If yes, then CSV storage is accessed via C:\ClusterStorage\VolumeXX where "XX" is the CSV volume number.

You can find the volume number CSV association in Failover Cluster Manager.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hyper-V

From novice to tech pro — start learning today.