unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ian Eure <ian@retrospec.tv>
To: help-guix@gnu.org
Subject: Problems making a bootable aarch64-linux system image
Date: Wed, 01 Jan 2025 12:55:08 -0800	[thread overview]
Message-ID: <87h66iuudv.fsf@retrospec.tv> (raw)

Hi folks,

I’m trying to get Guix System running in a QEMU VM on Apple ARM64 
hardware[1].  This has been much more challenging than I expected, 
and I haven’t been able to get it working at all.  I’m completely 
stuck and could use some advice and/or a working configuration I 
can hack on.

I’ve tried multiple paths to get this working, including building 
both installer and system images on arm64 and amd64 hardware.  My 
current approach is to make a bootable qcow2 system image using 
Guix as a foreign package manager on top of Debian running in a VM 
on the ARM hardware.  This is my image definition: 
https://paste.debian.net/1342063/

It’s buildable with:

  guix time-machine 
  --commit=96cd163c14e68c66c6a4cf0b18261fc454f8c1ba -- system 
  image vakum.scm

(Commits beyond 96cd163c14e68c66c6a4cf0b18261fc454f8c1ba fail, 
because guix tests are currently broken on aarch64-linux; see 
#75205)

This produces an image which boots to GRUB, but fails to boot the 
system.  It seems that the framebuffer console is initialized, 
since I see the QEMU window resize, but then I get a blinking 
cursor in the upper-left and nothing else.

Does anyone have pointers/advice/working configs for this I can 
hack on?  Any help would be greatly appreciated.

Thanks,

  -- Ian

[1]: My work requires everyone to use a Mac, unfortunately.


             reply	other threads:[~2025-01-01 20:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-01 20:55 Ian Eure [this message]
2025-01-02  9:03 ` Problems making a bootable aarch64-linux system image Christopher Baines
2025-01-02 17:28   ` Ian Eure
2025-01-02 18:35     ` Ian Eure

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=87h66iuudv.fsf@retrospec.tv \
    --to=ian@retrospec.tv \
    --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).