> On 24.03.2022 10:42 'Johannes Graumann' via qubes-users > <[email protected]> wrote: > > > > On 24.03.2022 09:53 'Johannes Graumann' via qubes-users > > <[email protected]> wrote: > > > > > > > On 22.03.2022 17:22 unman <[email protected]> wrote: > > > > > > > > > You have to include a call to qvm-volume in your state file. > > > > > > 'qvm-volume extend QUBE:private 50G': > > > cmd.run > > > > Super! Thank you! > > 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 ...`
For me this works: set size manually for one VM, check the "real" byte level size using `qvm-volume i QUBE:private` and use the "real" full number rather than the `G`-shorthand ... inconvenient. If `qvm-volume` allows to set using shorthands, it also should take care of using that info when checking. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/920091549.657939.1648115740297%40office.mailbox.org.
