Why Does Hyper-V Take A Kabillion Years To Delete A Virtual Machine?
Make no mistake about it.
I personally think Hyper-V is a seriously kickass slice of awesome from Microsoft. And if you aren’t at least checking it out, you’re really, truly and seriously missing out.
But it is abso-freaking-lutely INSANE how long it takes Hyper-V to fully delete a virtual machine if it has more than say…2 snapshots in it.
While doing some wickedly massive content dev recently, I was having to export some fairly large and semi-complex virtual machines, then fully wipe out them out before importing other fairly large and semi-complex virtual machines back in.
The export and import phases were awesome. Easily Hyper-V’s second best feature, only slightly behind the new snapshot feature.
But I literally would be waiting HOURS for the more involved virtual machines to finish detroying/merging/whatever.
Call me crazy…
But if I tell Hyper-V to “Delete” a given virtual machine, how freaking hard can it be to simply…oh I don’t know…dump the freaking contents of the virtual machine directory, and then clean its references out of Hyper-V?
|| posted by chris under clueless, kma, thumbs down, virtualization || || ||
