<damo22>qemu-system-i386 -M q35,accel=kvm -m 4096 -net user,hostfwd=tcp::8888-:22 -net nic -curses <damo22>it may still work with x86_64 actually <dragestil>i got qemu-system-i386, and ran the command in the qemu link above, but got the same error. i'm going to try your command <damo22>can you paste a screenshot of the terminal when it fails <dragestil>will do once your command has finished running <dragestil>i assume it is not a good idea to boot the same image simultaneously with two qemu commands <dragestil>now i'm getting a different error: start ext2fs: ext2fs: device:hd0s2: No such device or address <dragestil>this is what i ran: qemu-system-i386 -M q35,accel=kvm -m 4096 -net user,hostfwd=tcp::8888-:22 -net nic -curses debian-hurd-20210219.img <damo22>hmm you can try my full command: <damo22>qemu-system-i386 -M q35,accel=kvm -m 4096 -net user,hostfwd=tcp::8888-:22 -net nic -curses -drive id=udisk,file=debian-hurd-20210219.img,format=raw,if=none -device ide-hd,drive=udisk,bootindex=1 <dragestil>i ran your full command and it seems to be stuck at the same place <damo22>it should be text based using curses <dragestil>yeah, one moment as i have to remove all the leading spaces <damo22>yeah looks like the config is incorrect and should be pointing to sd0s2 <dragestil>this is the result when i run the original command from the qemu page on hurd wiki, with an extra curses <dragestil>looks like the issue is related to hd0s2 in this case too <dragestil>original command with s/kvm/qemu-system-x86_64 -enable-kvm/ though i386 produces the same result iirc <damo22>you can edit the config and root=/dev/sd0s2 <dragestil>i replaced one occurrence of hd0s2 by sd0s2. now it complains "device:sd0s2: No such device or address". I'll try again to see whether i should prepend a /dev in the config <dragestil>the part where i edited says "root=device:hd0s2" <dragestil>changing it to root=device:/dev/sd0s2 result in the same error, I'll try root=/dev/sd0s2 <dragestil>now it's showing a different error "ext2fs: /dev/sd0s2: gratuitous error" <dragestil>but i got the "device:sd0s2: No such device or address" <damo22>but your filesystem needs checking <dragestil>so shall i run `e2fsck /dev/hd0s2` in the maintenance shell? <dragestil>is it possible that the image i downloaded is corrupt? <damo22>its not corrupt, it just needs checking, ext2 is fragile <damo22>it can happen easily if you dont clean shutdown and umount <dragestil>strange the -curses produce different errors from when you run without -curses <dragestil>looks like the debian-hurd image does not have a gui <damo22>it should update the grub config so you dont have to edit grub anually every boot <dragestil>well the problem was the file system fsck anyway ***roptat_ is now known as Guest5707
***Guest5707 is now known as roptat
***john__ is now known as gaqwas