IRC channel logs

<Gooberpatrol66>janneke: sorry not sure who to ask this

<Gooberpatrol66>janneke: is it intended that it should not be possible to login to the childhurd vm? i am unable to login despite entering the correct password

<damo22>Gooberpatrol66: i assume the password is provided in the build config?

<Gooberpatrol66>damo22: i have an os definition for the childhurd in my config.scm

<Gooberpatrol66>damo22: (password (crypt "password" "$6$abc"))

<Gooberpatrol66>i enter "password" in the login and it fails

<Gooberpatrol66>it used to work

<damo22>it should be one of those two strings

<damo22>the other one is probably the salt

<Gooberpatrol66>the second one is supposed to be the salt

<Gooberpatrol66>neither work as the password

<damo22>ok

<damo22>did you change it?

<Gooberpatrol66>yes i've tried with other passwords

<damo22>idk

<Gooberpatrol66> https://pastebin.com/AwXezpLs

<janneke>Gooberpatrol66: i never tried with a password, always using ssh keys

<Gooberpatrol66>janneke: hmm, i also tried logging in with tigervnc and it didn't work

<Gooberpatrol66>seems like the user permissions are broken and not just ssh

<janneke>Gooberpatrol66: is password login enabled at all in the ssh config?

<janneke>ah weird

<Gooberpatrol66>janneke: yes, see the pastebin

<janneke>check

<Gooberpatrol66>i ssh the vm and it asks for the password

<Gooberpatrol66>Authentications that can continue: publickey,password

<youpi>Gooberpatrol66: does the auth.log file perhaps say something?

<Gooberpatrol66>youpi: method for viewing that file without ability to login?

<youpi>hard-shutdown the vm and mount it

<youpi>(after waiting 30s for the sync)

<Gooberpatrol66>is the childhurd fs persistent? it might not be

<youpi>where did you store it?

<Gooberpatrol66>um, i'm actually trying to figure that out

<janneke>Gooberpatrol66: no, the chilhurd is run with --snapshot

<Gooberpatrol66>ok

<janneke>(unless you changed something)

<Gooberpatrol66>it's a shepherd service

<Gooberpatrol66>if it's mutable then it's not stored in /gnu/store i guess, where is it stored?

<janneke>it's in the store, that's why usinhg --snapshot is needed

<Gooberpatrol66>janneke: so is it like overlayfs where there's a mutable layer on top? or does it store a whole new disk image when it shuts down?

<janneke>Gooberpatrol66: it's ephemeral, it's gone when you quit qemu

<Gooberpatrol66>ok that's what i meant by persistent, the data surviving reboot

<janneke>you can always look at /proc/<pid>/cmdline with <pid> from herd status childhurd

<janneke>you can copy the /gnu/store/...disk-image somewhere, make it writeable, and run the qemu command without --snapshot if you want persistent storage

<Gooberpatrol66>janneke: seems like it's not booting properly?

<Gooberpatrol66>"System lacks support for 'signalfd'; using fallback mechanism.

<Gooberpatrol66>irq handler [11]: new delivery port f56649d8 entry f52e78a0

<Gooberpatrol66>ext2fs: part:1:device:hd0:warning: MOUNTED READ-ONLY: MUST USE 'fsysopts --writable'

<janneke>Gooberpatrol66: the signalfd error is to be expected

<janneke>did you make the image writable after copying it?

<Gooberpatrol66>janneke: is chmod +w enough?

<Gooberpatrol66>says still mounted read-only

<janneke>yes that should be enough

<Gooberpatrol66>chattr -i didn't work

<damo22>mount / -o remount,rw

<Gooberpatrol66>i need to boot it mutable in qemu so i can get the auth.log

<Gooberpatrol66>i don't have a command line in the vm

<janneke>Gooberpatrol66: ah right, i'm sorry; you cannot easily start the childhurd image by hand because on startup it first waits for the secret service

<janneke>if you want to start it by hand you should build a qemu image by hand

<Gooberpatrol66>alright

<janneke>something like guix system image --image-type=hurd-qcow2 --image-size=5G gnu/system/examples/bare-hurd.tmpl

<janneke>sorry 'bout that

<Gooberpatrol66>i think the fs is mutable now

<Gooberpatrol66>i don't see a login prompt in vnc

<Gooberpatrol66>just some hd0: ide0: irq handler [11]: messages

<Gooberpatrol66>same thing with devel-hurd.tmpl

<janneke>Gooberpatrol66: i just tried with a895cc4c5b and building bare-hurd.tmpl and following the instructions works for me, ie, gives a login prompt in the qemu gui

<Gooberpatrol66>janneke: ok it works with that version and i can login

<Gooberpatrol66>not sure the difference with the childhurd image causing the login issue

<janneke>as i said, the childhurd image won't present a login prompt or allow login by ssh if started by hand

<janneke>it works fine for me adding authorized-keys to the ssh config

<Gooberpatrol66>ok it works with the key, maybe i wasn't specifying it or something

<Gooberpatrol66>still weird the password doesn't work tho

<Gooberpatrol66>exit

<Gooberpatrol66>whoops wrong window

<janneke>Gooberpatrol66: yay!

<Gooberpatrol66>thanks

<janneke>Gooberpatrol66: when running qemu manually, i usually use --nographic, see https://guix.gnu.org/manual/devel/en/html_node/Bootloader-Configuration.html (or for exaple https://lists.gnu.org/archive/html/guix-patches/2023-05/msg01049.html for a full command)

IRC channel logs

2025-01-28.log