Turns out, this does not generally work. The first time the command runs (and <REVISION>, the target storage size is really bigger than what is set) everything is fine, but as the shorthands like `G` do not reflect what's really set (in bytes) under the hood such a statement fails on every further run, as `qvm-volume` returns an error: `For your own safety, shrinking of private is disabled ...`