From: Brian O'Keefe <okeefe@cybermesa.com>
To: help-guix@gnu.org
Subject: Re: Guix system on AQEMU HD fills
Date: Mon, 18 Mar 2024 18:35:39 -0600 [thread overview]
Message-ID: <403349be-08f5-4d18-b094-5de7e49f020a@cybermesa.com> (raw)
In-Reply-To: <8776d9e6-46b4-4ccb-9928-a159d3751df2@owenh.net>
Thanks Owen. I used the .iso image in the QEMU install. I will Run `guix
gc -d` to delete all old generations. I have no need to rollback (yet!)
I'm not using VBox as I have in the past, wanting to using FOSS apps.
I'll keep track of disk usage. Luckily this is experimental and not a
production set-up.
On 3/18/24 04:48PM, Owen T. Heisler wrote:
> On 3/18/24 15:56, Brian O'Keefe wrote:
>> I've been installing and reinstalling the latest GUIX OS in AQEMU.
>
>> yesterday I got a warning from my Ubuntu host that my HD was
>> dangerously low.
>
>> I saw that my ~/.aqemu folder was packed and the culprit was the
>> virtual GUIX machine which had far exceeded its 25GB capacity.
>
> If you created a 25 GB hard drive with AQEMU (that's a QEMU front-end,
> right?), then the `guix.qcow2` hard drive image shouldn't get much
> bigger than 25 GB. However if AQEMU is using qcow2 snapshots, then the
> image will grow as much as necessary to keep all the snapshot data.
>
>> It also seems that with each "guix pull" or "guix refresh" or "guix
>> upgrade" more and more data is being stored.
> Run `guix gc -d` to delete all old generations. You will not be able
> to roll-back the Guix system to a previous generation once you have
> deleted it.
>
>> Why that affects my host OS, I don't know
> Yeah, that seems odd. The only thing that comes to my mind is qcow2
> snapshots as I mentioned above.
>
>
--
prev parent reply other threads:[~2024-03-19 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 20:56 Guix system on AQEMU HD fills Brian O'Keefe
2024-03-18 22:48 ` Owen T. Heisler
2024-03-19 0:35 ` Brian O'Keefe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=403349be-08f5-4d18-b094-5de7e49f020a@cybermesa.com \
--to=okeefe@cybermesa.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).