unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: Ellen Papsch <ellen.papsch@wine-logistix.de>,
	Guix-devel <guix-devel@gnu.org>
Subject: Re: Using the Hetzner Cloud
Date: Tue, 18 Feb 2020 18:35:21 +0100	[thread overview]
Message-ID: <e78a172e-1383-5828-4c6b-331844afd89f@web.de> (raw)
In-Reply-To: <31fbafeb5a408e361b65861dda17bd0c65cd5118.camel@wine-logistix.de>

On 17.02.20 17:55, Ellen Papsch wrote:> a few days ago I requested the
Guix installer from Hetzner as well. I
> gave them the ISO URL from Guix website. They mounted it without
> modification, which prevented boot due to the image being compressed. I
> had to supply the uncompressed image, which booted fine.
>
> The installer was not able to install right away. I could complete all
> the GUI steps. When it came to guix system init, it bailed with the
> message that an initrd-module may be missing. System init (and the
> subsequent boot) worked fine with:
>
> (initrd-modules (append (list "virtio_pci"
>                               "virtio_scsi")
>                         %base-initrd-modules))

AFAIK it's fixed in Guix master. But 1.0.1 is missing the patch. It's
time for new release :)

> BTW, the VGA console is very limited, you can't select text or send
> special key strokes, e.g. control keys. It suffices for activating SSH
> though :-)

The console is limited but was always good enough for my use cases :)

> Hetzner added the image only for me, which is a hindrance for Guix
> adoption. Another limitation is that I can't create new servers right
> away without going through installation. I can dance around it by
> creating a snapshot of a template server and creating the new server
> from that snapshot, then reconfiguring the system (or doing a deploy, I
> want to try that yet).
>
> So, doing Guix is a little more inconvenient than a simple, plain
> Debian. I can still recommend it, though you may find Hetzner not
> meeting your demands in general: The cloud offerings have a rather low
> cpu/memory ratio (0.25 cpu/1G RAM) and it's not configurable.

Going through the installer all the time if you have more servers is
annoying. But for smaller setups with one or two servers pretty okay.

  parent reply	other threads:[~2020-02-18 17:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 13:47 Using the Hetzner Cloud Jonathan Brielmaier
2020-02-17 16:55 ` Ellen Papsch
2020-02-17 17:15   ` Alex Sassmannshausen
2020-02-18 11:44     ` Ellen Papsch
2020-02-18 11:58     ` Giovanni Biscuolo
2020-02-19 13:48       ` Alex Sassmannshausen
2020-02-21 18:00         ` Giovanni Biscuolo
2020-02-21 18:20           ` Alex Sassmannshausen
2020-02-18 17:38     ` Jonathan Brielmaier
2020-02-17 20:16   ` Christopher Baines
2020-02-18 17:35   ` Jonathan Brielmaier [this message]
2020-02-17 20:12 ` Christopher Baines
2020-02-17 20:39   ` Ricardo Wurmus
2020-02-17 21:28     ` Christopher Baines
2020-02-24 21:45   ` Ludovic Courtès

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=e78a172e-1383-5828-4c6b-331844afd89f@web.de \
    --to=jonathan.brielmaier@web.de \
    --cc=ellen.papsch@wine-logistix.de \
    --cc=guix-devel@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.
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).