Open rob-metalinkage opened 7 years ago
I am having the same issue. I wonder if the app is configured to do both VMDKs and VDIs? It's much easier to expand a VDI so I think it may only be compatible with that. Also the vagrant image starts up far to quickly considering the disk operation.
Attempted to use this with a couple of different base boxes and no change in disk size seems to have been recorded.
1) should any relevant messages appear in the vagrant up log if configured correctly? 2) after install, should df -h be sufficient to see new disk size? 3) if "Depending on the guest, you may need to resize the partition and the filesystem from within the guest. At present the plugin only resizes the underlying disk." applies, how does one check the disk size is actually available, and a pointer to docs on parted (and adding necessary tools to the vagrant file provisioning)
(also - is there anyway of knowing the configured disk size on a base box? doesnt seem to be visible except in a couple of comments on the register)