GNU bug report logs - #66053
Childhurd fails to run inside ‘guix system vm’

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#66053: closed (Childhurd fails to run inside ‘guix
 system vm’)
Date: Mon, 18 Sep 2023 21:45:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Mon, 18 Sep 2023 23:44:13 +0200
with message-id <87y1h3f976.fsf <at> gnu.org>
and subject line Re: bug#66053: Childhurd fails to run inside ‘guix system vm’
has caused the debbugs.gnu.org bug report #66053,
regarding Childhurd fails to run inside ‘guix system vm’
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
66053: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66053
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ludovic Courtès <ludovic.courtes <at> inria.fr>
To: bug-guix <at> gnu.org
Subject: Childhurd fails to run inside ‘guix system
 vm’
Date: Sun, 17 Sep 2023 17:21:33 +0200

Hello!

I’m failing to run a childhurd inside a ‘guix system vm’ GNU/Linux VM as
of fc3a53525ab3dcaf7c22eec8d62294017f9760fe.

--8<---------------cut here---------------start------------->8---
Sep 17 17:03:25 localhost shepherd[1]: [qemu-system-i386] qemu-system-i386: Slirp: Failed to send packet, ret: -1 
Sep 17 17:03:37 localhost shepherd[1]: [qemu-system-i386] qemu-system-i386: Slirp: Failed to send packet, ret: -1 
Sep 17 17:03:43 localhost shepherd[1]: [qemu-system-i386] qemu-system-i386: Bad ram pointer 0x7f739ac0001e 
Sep 17 17:03:43 localhost shepherd[1]: secret service: invalid handshake #<eof> 
Sep 17 17:03:43 localhost shepherd[1]: Service hurd-vm could not be started. 
Sep 17 17:03:43 localhost shepherd[1]: Service hurd-vm failed to start. 
--8<---------------cut here---------------end--------------->8---

When I run it by hand with KVM on my bare-metal GNU/Linux machine, it’s
all good: 👍

--8<---------------cut here---------------start------------->8---
$ "/gnu/store/1rg1fb9mj65rh82467vwlrkmi12p4v89-qemu-minimal-8.1.0/bin/qemu-system-i386" "-m" 2048 "--device" "rtl8139,netdev=net0" "--netdev" "user,id=net0,hostfwd=tcp:127.0.0.1:11004-:1004,hostfwd=tcp:127.0.0.1:10022-:2222,hostfwd=tcp:127.0.0.1:15900-:5900" "--snapshot" "--hda" "/gnu/store/iqacww23byvw9c5ssja9fkx6m4s057b0-disk-image" "--no-reboot" --enable-kvm
VNC server running on 127.0.0.1:5900
--8<---------------cut here---------------end--------------->8---

However, the same thing *without* KVM (as happens within ‘guix system
vm’) reproduces the “Bad ram pointer” issue:

--8<---------------cut here---------------start------------->8---
$ "/gnu/store/1rg1fb9mj65rh82467vwlrkmi12p4v89-qemu-minimal-8.1.0/bin/qemu-system-i386" "-m" 2048 "--device" "rtl8139,netdev=net0" "--netdev" "user,id=net0,hostfwd=tcp:127.0.0.1:11004-:1004,hostfwd=tcp:127.0.0.1:10022-:2222,hostfwd=tcp:127.0.0.1:15900-:5900" "--snapshot" "--hda" "/gnu/store/iqacww23byvw9c5ssja9fkx6m4s057b0-disk-image" "--no-reboot" 
VNC server running on 127.0.0.1:5900
qemu-system-i386: Bad ram pointer 0x7fa930e0001e
Aborted
--8<---------------cut here---------------end--------------->8---

Good news: I found a workaround!  Just use the x86_64 emulator:

--8<---------------cut here---------------start------------->8---
$ "/gnu/store/1rg1fb9mj65rh82467vwlrkmi12p4v89-qemu-minimal-8.1.0/bin/qemu-system-x86_64" "-m" 2048 "--device" "rtl8139,netdev=net0" "--netdev" "user,id=net0,hostfwd=tcp:127.0.0.1:11004-:1004,hostfwd=tcp:127.0.0.1:10022-:2222,hostfwd=tcp:127.0.0.1:15900-:5900" "--snapshot" "--hda" "/gnu/store/iqacww23byvw9c5ssja9fkx6m4s057b0-disk-image" "--no-reboot" 
VNC server running on 127.0.0.1:5900
--8<---------------cut here---------------end--------------->8---

Obviously, I have no clue why that works, but who cares, right?  :-)

Thoughts?

Ludo’.

[Message part 3 (message/rfc822, inline)]

From: Ludovic Courtès <ludo <at> gnu.org>
To: 66053-done <at> debbugs.gnu.org
Cc: Janneke Nieuwenhuizen <janneke <at> gnu.org>
Subject: Re: bug#66053: Childhurd fails to run inside ‘guix system vm’
Date: Mon, 18 Sep 2023 23:44:13 +0200

Ludovic Courtès <ludovic.courtes <at> inria.fr> skribis:

> When I run it by hand with KVM on my bare-metal GNU/Linux machine, it’s
> all good: 👍
>
> $ "/gnu/store/1rg1fb9mj65rh82467vwlrkmi12p4v89-qemu-minimal-8.1.0/bin/qemu-system-i386" "-m" 2048 "--device" "rtl8139,netdev=net0" "--netdev" "user,id=net0,hostfwd=tcp:127.0.0.1:11004-:1004,hostfwd=tcp:127.0.0.1:10022-:2222,hostfwd=tcp:127.0.0.1:15900-:5900" "--snapshot" "--hda" "/gnu/store/iqacww23byvw9c5ssja9fkx6m4s057b0-disk-image" "--no-reboot" --enable-kvm
> VNC server running on 127.0.0.1:5900
>
>
> However, the same thing *without* KVM (as happens within ‘guix system
> vm’) reproduces the “Bad ram pointer” issue:
>
> $ "/gnu/store/1rg1fb9mj65rh82467vwlrkmi12p4v89-qemu-minimal-8.1.0/bin/qemu-system-i386" "-m" 2048 "--device" "rtl8139,netdev=net0" "--netdev" "user,id=net0,hostfwd=tcp:127.0.0.1:11004-:1004,hostfwd=tcp:127.0.0.1:10022-:2222,hostfwd=tcp:127.0.0.1:15900-:5900" "--snapshot" "--hda" "/gnu/store/iqacww23byvw9c5ssja9fkx6m4s057b0-disk-image" "--no-reboot" 
> VNC server running on 127.0.0.1:5900
> qemu-system-i386: Bad ram pointer 0x7fa930e0001e
> Aborted
>
>
> Good news: I found a workaround!  Just use the x86_64 emulator:

Done in 5e0ae2684615b6d10751390420e7db296785112b!

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.