Repository navigation
Replies: 1 comment
|
So right now - pause just saves the ram and whole disk into a .smolcheckpoint that resume HAS to unpack. Meaning it can lead to failures with full disk later on as youve experienced.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi, I've started using smolvm as a way to isolate my workload on my Mac. By that I mean basically all my development activity which requires compiling Rust, so I need all my CPU cores and all the RAM I have on my host. At the same time with smolvm I can reclaim my RAM so that my host apps can run as well.
Now the issue is the disk space: Rust requires a lot of it and I don't have plenty. And when I pause my smolvm it saves both RAM and disk to .smolcheckpoint file. Yesterday I had an issue with resuming my smol VM - I simply had not enough space to unpack that .smolcheckpoint. There is no option to discard that state either.
Now I wonder, maybe I am supposed to store all my files on my host and simply mount directories I need? But can't this result in inconsistency issues if my files change while my VM is paused? Maybe I miss something? Or maybe smolvm isn't designed for that type of usage at all? I'm looking for an advice 🙏
All reactions