all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "J. Sims" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 61986@debbugs.gnu.org
Subject: bug#61986: Installing qemu-binfmt with support for emulating the host architecture breaks everything
Date: Sun, 05 Mar 2023 18:33:07 +0000	[thread overview]
Message-ID: <fibQOMbqS2rsKtGIPO_6wzE48Nlx5gGEuTMGTPsuQPYzbu9rRPyrMVClxXSXxMdTjg3bxHXLYL3lZuxiul81cO86koC9fs1Z4mlbVk56_AU=@protonmail.com> (raw)

Hey y'all,

I recently setup virtualization on my Guix machine (both libvirt and qemu, for different purposes). While configuring libvirt (via virt-manager), I got a bit confused about how to make things work and also installed qemu-binfmt for x86_64, the host architecture. Upon my next reboot, however, I reached a fully-booted TTY and was unable to do anything else. GDM was not launching, and if I attempted to login to the TTY itself, I was greeted by an error message like the following:

"cannot execute /gnu/store/path-to-something/bin/thing: Too many layers of symlinks"

After some misadventures, I have finally narrowed down that the cause of this issue was having x86_64 in the list of qemu-binfmt-configuration platforms while running on x86_64. I assume that including the host architecture in the list of platforms for qemu-binfmt will do this regardless of architecture, but cannot currently test this.

Here's what I believe to be a minimum reproducible example for x86_64:

```
(operating-system
 ...
 (services (cons*
             (service qemu-binfmt-service-type
                      (qemu-binfmt-configuration
                        (platforms (lookup-qemu-platforms "x86_64"))))
           ...)
 ...)
```

Good luck,
Juli




             reply	other threads:[~2023-03-05 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 18:33 J. Sims via Bug reports for GNU Guix [this message]
2024-05-23 18:21 ` bug#61986: qemu-binfmt-service-type should protect against adding platforms for target system Richard Sent

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='fibQOMbqS2rsKtGIPO_6wzE48Nlx5gGEuTMGTPsuQPYzbu9rRPyrMVClxXSXxMdTjg3bxHXLYL3lZuxiul81cO86koC9fs1Z4mlbVk56_AU=@protonmail.com' \
    --to=bug-guix@gnu.org \
    --cc=61986@debbugs.gnu.org \
    --cc=jtsims@protonmail.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.