In preparation for attempting to compress my Windows image (30GB, 90GB!!! on disk), I ran the "Merge snapshots" operation in the Image tool. This was launched yesterday afternoon and I left it to it's own devices. Returning home several hours later, the progress bar was complete, yet it was still running with high CPU utilization, so I again went out and left it running overnight. 34 hours later, it is STILL going and I do not even have the option to cancel, although I'm not sure I want to at this stage, for fear of rendering the image unusable.
All the same, I feel I may have to force quit the process at some point as I'll be back to work tomorrow - obviously there's a lot of data in that image and I saw an article from a user with a 47.5GB image reporting a 12-hour duration for the process, but I've gone way beyond twice that period now! Why does this take so ridiculously long to complete? And furthermore, why does the image need to expand to _triple_ the size of the available VM disk?
Additional info: running build 5582, 16GB free out of 186GB on drive (hence my attempts to compact the Parallels image).
All the same, I feel I may have to force quit the process at some point as I'll be back to work tomorrow - obviously there's a lot of data in that image and I saw an article from a user with a 47.5GB image reporting a 12-hour duration for the process, but I've gone way beyond twice that period now! Why does this take so ridiculously long to complete? And furthermore, why does the image need to expand to _triple_ the size of the available VM disk?
Additional info: running build 5582, 16GB free out of 186GB on drive (hence my attempts to compact the Parallels image).
Last edited: