![]() I'd manually list and nuke any such snapshots prior to requesting the modified disk size. to open the corresponding dialogue window then remove Snapshots to start editing the disk size. If the VM has Snapshots the following notification window will appear. I'd just work around this myself if there were a way for me, within the context of the Vagrantfile's main block, to run prlctl commands (like prl.customize) but where I could get the output. Go to the Hardware tab, select Hard Disk which requires increasing the size then click Properties. For this exercise we want to remove the swap partition an extend /dev/sda1 to the whole disk. Perhaps force me to include some extra parameter that essentially says, "I understand the risk associated with deleting any such snapshots of the base box's disk, but my circumstances are such that I'm declaring it's okay". Here's the list of steps for a simple scenario where you have two partitions, /dev/sda1 is an ext4 partition the OS is booted from and /dev/sdb2 is swap. I'd love a way to have vagrant-parallels give me the option to explicitly request any/all such snapshots be nuked ( prlctl snapshot-delete. ![]() Only the snapshot (from prior instances of the VM that did use linked cloning of the base box, but have since all been nuked) gets in the way. I can almost use it to enlarge my disk by disabling linked cloning and using prl.customize to set a new/larger disk size. Symptoms You are unable to resize a Virtual Machine hard drive because of the error message: Unable to resize the last volume. We have a per-developer Vagrantfile.local that we can define to override general settings. However, a subset of us now need larger disks. I used to be okay with our company-wide Vagrantfile that used linked cloning. This one VM references my one and only base box. The reality is, I only need/use exactly 1 VM (at a time I often vagrant destroy / vagrant up as necessary). ![]() The fact that I used to have a version of my VM that used linked cloning is vestigial. So, I understand the underlying difficulty in accomplishing this mentioned by said, there are some of us where the danger, ".unfortunately we can't remove this snapshot, because that will corrupt all existing linked clones." is irrelevant.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |