unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: Florian Hoertlehner <hoertlehner@gmail.com>
Cc: 52680@debbugs.gnu.org
Subject: bug#52680: installer error
Date: Mon, 27 Dec 2021 13:45:06 +0100	[thread overview]
Message-ID: <878rw6tdwt.fsf@gnu.org> (raw)
In-Reply-To: <878rw6xxpu.fsf@gnu.org> (Mathieu Othacehe's message of "Mon, 27 Dec 2021 09:23:41 +0100")

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]


Hey,

> guix system image -t qcow2 gnu/system/install.scm

So, I produced a qcow2 installation image this way, imported it in
DigitalOcean, then created a droplet out of it.

The qcow2 image is resized to the droplet disk image size, 25GiB in my
case, and appears as vda disk. There is also an empty vdb disk. In the
installer partitioning page, vda is hidden as this is the installation
device but vdb appears.

Trying to proceed with vdb fails and leads to the backtrace you sent
us. Two things here:

1. We should hide vdb as it is an empty drive, maybe by requiring a
minimal available space. Josselin, what do you think about it?

2. As the qcow2 installation image is also the main VM drive, it will be
hard to install Guix System this way. You might prefer to generate a
complete disk-image that suit your needs and use it directly on
DigitalOcean, as described here:
https://othacehe.org/hosting-a-blog-using-only-scheme.html.

Thanks,

Mathieu

[-- Attachment #2: Screenshot from 2021-12-27 13-31-53.png --]
[-- Type: image/png, Size: 26778 bytes --]

  reply	other threads:[~2021-12-27 12:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20 13:22 bug#52680: installer error Florian Hoertlehner
2021-12-27  8:23 ` Mathieu Othacehe
2021-12-27 12:45   ` Mathieu Othacehe [this message]
2021-12-27 16:25     ` Josselin Poiret via Bug reports for GNU Guix
2021-12-27 18:18       ` Mathieu Othacehe
2022-02-02 16:37         ` Mathieu Othacehe

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=878rw6tdwt.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=52680@debbugs.gnu.org \
    --cc=hoertlehner@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).