Things That Come To Mind With: Hyper-V

merge

Anyone who has been in technology for any length of time has had those moments while working a problem when you say “Why can’t this product do what seems to be very simple.” 

Today brought up a couple of these thoughts for Hyper-V.

The first is live snapshot merging:  Why do I need to shutdown my VMs in order to merge an AVHD file into the parent disk?  With technologies like storage migration already in the product with the aid of SCVMM, why can’t there be some behind the scenes merge process followed by a quick disconnection and then reconnection of the new merged VHD. 

The second is VHD shrinking.  I know you can mount a VHD and shrink the space of the partition within storage administrator, but shrinking the overall size of the volume really isn’t possible unless you use some sort of cloning utility or partition resizing utility.  Especially after a physical to virtual migration, the original physical could be 146GB or 300GB and grossly underutilized.   For production systems I use Fixed disks, for better or worse, and keeping these fully expanded would be a big waste of disk resources.  Live shrinking would be preferred with similar technologies as above, but even an offline option would be welcomed.

Granted, there may be more to executing this technology than I think, but there are folks out there much smarter than I working on the solution to these and other “holes” in the product.

Advertisements
This entry was posted in Hyper-V and tagged , , , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s