unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ben Sturmfels <ben@sturm.com.au>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Guix on a cloud VM
Date: Thu, 02 Sep 2021 10:26:37 +1000	[thread overview]
Message-ID: <87czpr95bq.fsf@sturm.com.au> (raw)
In-Reply-To: <87h7f66pc3.fsf@gnu.org>

Thanks Mathieu! We've discussed further on IRC, but summarising below
for the list.

On Tue, 31 Aug 2021, Mathieu Othacehe wrote:

> Oh, too bad. You could maybe contact Binary Lane support to find out
> why? Have you tried to boot your qcow2 image on your machine with QEMU?
> The command line would look like the one presented here:
> https://guix.gnu.org/manual/en/html_node/Installing-Guix-in-a-VM.html.
>
>> 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?
>
> No it is not possible currently, due to how Grub is installed on Guix
> System images. However, you should be able to resize your partition
> manually using fdisk and resize2fs, see below :).

I contacted Binary Lane's support and they advised that while they
didn't support QCOW2, I could resolve the resizing issue by using their
"BYO OS" configuration, rather than their built-in image configurations
like "Debian". Doing so disables their auto-magic storage resizing
feature which seems to choke on the multi-partition image. I can live
with uploading a 1.5GB raw image and then resizing the partition. :)

Noting that you also have a working demo of a single partition image
type, that we may see in the near future.

Thanks very much for your help!

Regards,
Ben


  reply	other threads:[~2021-09-02  0:42 UTC|newest]

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