-------- Forwarded Message -------- From: claire <[email protected]> To: Alperen Erkan <[email protected]> Subject: Re: debian-hurd on qemu won't work Date: 09/25/2026 11:37:11 PM
> Okay, it's just that I've already booted HURD with QEMU… but I still > get the input/output error. > > On Sat, 2026-09-26 at 00:31 +0300, Alperen Erkan wrote: > > Congratulations on resolving the raw format issue! > > > > The new error (“host forwarding rule could not be set”) usually > > occurs because port 2222 on your host machine is already in use by > > another process (for example, an existing SSH daemon or another > > QEMU instance). > > > > Here are a few ways to resolve this: > > > > 1. Change the Host Port > > Try mapping to a different port on your host machine, such as 2223 > > or 2224: > > > > qemu-system-amd64 -m 4G \ > > -drive format=raw,file=$(echo debian-hurd-*.img) \ > > -net user,hostfwd=tcp:127.0.0.1:2223-:22 \ > > -net nic,model=e1000 > > > > (You can then use port 2223 to connect via SSH: ssh -p 2223 > > [email protected]) > > 2. Check Whether Port 2222 Is in Use > > > > You can check what is using port 2222 on your host machine by > > running the following command: > > > > sudo lsof -i :2222 > > > > If the port is being used by something else, you can stop that > > service or use a different port as shown above. > > > > Please let us know if you are able to boot up after changing the > > port! > > > > Kind regards, > > > > Alperen ERKAN > > > > > > On Sat, Sep 26, 2026 at 12:29 AM Alperen Erkan > > <[email protected]> wrote: > > > Hold on a moment, I’m sending you a detailed roadmap ;) > > > > > > On Sat, Sep 26, 2026 at 12:28 AM claire > > > <[email protected]> wrote: > > > > hello, > > > > > > > > i try with : > > > > claire@localhost:~/Documents/Hurd$ qemu-system-amd64 -m 4G - > > > > drive format=raw,file=$(echo debian-hurd-*.img) -net > > > > user,hostfwd=tcp:127.0.0.1:2222-:22 -net nic,model=e1000 > > > > > > > > but now : > > > > > > > > qemu-system-amd64: -net user,hostfwd=tcp:127.0.0.1:2222-:22: > > > > Could not set up host forwarding rule 'tcp:127.0.0.1:2222-:22' > > > > > > > > > > > > On Sat, 2026-09-26 at 00:20 +0300, Alperen Erkan wrote: > > > > > Hello Claire, > > > > > > > > > > That’s a good output—clear and informative. The possible > > > > > solution is as follows: > > > > > > > > > > Based on your terminal output, there are two main issues to > > > > > address: the explicit warning regarding the image format and > > > > > the KVM/virtualisation configuration. The step-by-step > > > > > process for resolving these is explained below: > > > > > > > > > > 1. Specify the Image Format Explicitly > > > > > > > > > > QEMU is issuing a warning because it assumes the image is in > > > > > raw format, which restricts write operations on block 0. You > > > > > can easily resolve this by adding `-drive format=raw` to your > > > > > command. > > > > > 2. Check Virtualisation / Nested Virtualisation Settings in > > > > > the BIOS > > > > > > > > > > You mentioned that you may have installed Debian Trixie > > > > > without enabling virtualisation in the BIOS, or perhaps you > > > > > are running it within a virtual machine (in which case nested > > > > > virtualisation must be enabled on the host machine). > > > > > > > > > > If you are using physical hardware: Restart your computer, > > > > > enter the BIOS/UEFI settings and enable Intel VT-x or AMD-V. > > > > > > > > > > If you are inside a virtual machine (VirtualBox, KVM, etc.): > > > > > Ensure that nested virtualisation is enabled for the virtual > > > > > machine itself. > > > > > > > > > > If KVM is not working or is not required: You can remove the > > > > > `--enable-kvm` option from the command to run QEMU in pure > > > > > emulation mode (it runs more slowly, but it will boot). > > > > > > > > > > Updated QEMU Command > > > > > > > > > > Try running this command (specify the format depending on > > > > > your BIOS/host machine configuration, and keep or remove > > > > > KVM): > > > > > > > > > > qemu-system-amd64 --enable-kvm -m 4G \ > > > > > -drive format=raw,cache=writeback,file=$(echo debian-hurd- > > > > > amd64-*.img) \ > > > > > -net user,hostfwd=tcp:127.0.0.1:2222-:22 \ > > > > > -net nic,model=e1000 > > > > > > > > > > (Note: If you are still receiving errors after enabling KVM > > > > > in the BIOS, try removing the --enable-kvm option to check > > > > > whether pure emulation boots successfully.) > > > > > > > > > > Please let us know the results! > > > > > > > > > > Good luck! > > > > > Alperen ERKAN > > > > > > > > > > > > > > > > > > > > On Fri, Sep 25, 2026 at 11:46 PM claire > > > > > <[email protected]> wrote: > > > > > > hi, > > > > > > > > > > > > i try qemu image but not work > > > > > > > > > > > > https://images.franceserv.fr/image/EZZ > > > > > > > > > > > > claire@localhost:~/Documents/Hurd$ qemu-system-amd64 -- > > > > > > enable-kvm -m 4G > > > > > > -drive cache=writeback,file=$(echo debian-hurd-*.img) -net > > > > > > user,hostfwd=tcp:127.0.0.1:2222-:22 -net nic,model=e1000 > > > > > > WARNING: Image format was not specified for 'debian-hurd- > > > > > > amd64- > > > > > > 20260314.img' and probing guessed raw. > > > > > > Automatically detecting the format is dangerous > > > > > > for raw > > > > > > images, write operations on block 0 will be restricted. > > > > > > Specify the 'raw' format explicitly to remove the > > > > > > restrictions. > > > > > > > > > > > > claire@localhost:~/Documents/Hurd$ lsmod | grep kvm > > > > > > kvm_intel 413696 3 > > > > > > kvm 1396736 2 kvm_intel > > > > > > irqbypass 12288 1 kvm > > > > > > claire@localhost:~/Documents/Hurd$ > > > > > > > > > > > > i think i install debian trixie without virtualization > > > > > > enabled in bios. > > > > > > > > > > > > i don't know how to do working qemu image > > > > > > > > > > > > kind regards, > > > > > > claire > > > > > > > > > > > > > > >
