unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ben Sturmfels <ben@sturm.com.au>
To: othacehe@gnu.org
Cc: help-guix <help-guix@gnu.org>
Subject: Guix on a cloud VM
Date: Tue, 31 Aug 2021 12:40:33 +1000	[thread overview]
Message-ID: <87tuj61egl.fsf@sturm.com.au> (raw)

Hi Mathieu (and CC'ing help-guix),

Thanks for your help on the Guix IRC yesterday! I'm still struggling
with getting the VM running as I'd like. I tried the ISO format as you
suggested, but my hosting service (Binary Lane) seems to treat this
somewhat-specially as a read-only format. I can "trick" it into
restoring from this image using their "clone" feature though. The
machine boots up fine but the result seems to be a read-only Guix where
/etc/fstab shows an iso9660 filesystem.

Backing up a little for context, I've tried qcow2 format which is lovely
and small, but fails to boot on my hosting service with "No bootable
devices".

I've also tried efi-raw which boots and runs smoothly, but fails to
resize later on my hosting service. (Resize is required because
otherwise I literally have to generate and upload a 20GB image.) I
suspect (but don't know for sure) that this is related to the additional
40M EFI partition created in the image before the root EXT4 partition.
The images provided by my hosting service only have a single EXT4
partition eg. Debian 10.

Do you know if it's possible to get `guix system image` to skip the EFI
partition when creating an efi-raw image?

A couple of other questions too:

Does the process in your blog post work for you if you go straight to
QCOW2 with `--image-type=QCOW2` rather than converting the efi-raw to
qcow2?

Are you able to later resize the storage via your DigitalOcean control
panel? This operation is failing for me currently.

Thanks again for your help and excellent blog post!

Ben

Reference for anyone else reading:

Mathieu's blog post:
https://othacehe.org/hosting-a-blog-using-only-scheme.html

My work-in-progress guix deploy experiments:
https://stumbles.id.au/getting-started-with-guix-deploy.html



             reply	other threads:[~2021-08-31 16:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31  2:40 Ben Sturmfels [this message]
2021-08-31  7:33 ` Guix on a cloud VM Mathieu Othacehe
2021-09-02  0:26   ` Ben Sturmfels
2021-09-02  4:31     ` Ben Sturmfels

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=87tuj61egl.fsf@sturm.com.au \
    --to=ben@sturm.com.au \
    --cc=help-guix@gnu.org \
    --cc=othacehe@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).