(Note: 5.2 was just released a few weeks ago, and looks like it should prevent the problem happening in the future by properly informing users that it isn't possible with snapshots). It looks like, for a resize, that a merge of all snapshots has to occur first - one user on that list details a workaround to maintain snapshots by cloning the VM. I haven't had to deal with the issue due to my dynamic disk sizes not being small from the start anymore (this is mostly an issue for my Windows VMs where the base disk may need significant size for the OS).
The issue is entirely detailed here: - the problem was caused because of having existing snapshots (which error message output was not detailing). I have had issues in the past when it has come to resizing VM disk storage.Unified Communications as a Service (UCaaS).Integration Platform as a Service (iPaaS).
0 kommentar(er)
