Re: GNU/Hurd installation
On Mon, 2023-01-16 at 00:01 -0500, Paul Smith wrote: > I just got a new GNU/Linux laptop for working at home: it has the > very latest Intel i9 CPU, NVMe disk, and all the trimmings. It's > running Ubuntu 22.04. Perhaps this is leading to issues. > > I have a GNU/Linux laptop at work with older hardware (circa 2018), > which is also still running Ubuntu 20.04, that I can try out on > Tuesday; maybe that will work better. The Hurd image loaded and started fine on my older laptop. So I guess Hurd doesn't properly support some part of my newer system, or maybe the virtualization layer has some problem with it. Anyway I see some failures so I'll look into them.
Re: GNU/Hurd installation
On Sun, 2023-01-15 at 22:47 +0100, Bruno Haible wrote: > Unfortunately, this magic pixie dust depends on your CPU model, > UEFI/BIOS settings, Linux host kernel version, and VirtualBox > version. I just got a new GNU/Linux laptop for working at home: it has the very latest Intel i9 CPU, NVMe disk, and all the trimmings. It's running Ubuntu 22.04. Perhaps this is leading to issues. I have a GNU/Linux laptop at work with older hardware (circa 2018), which is also still running Ubuntu 20.04, that I can try out on Tuesday; maybe that will work better. Beyond the Hurd issues I think the only outstanding issues I haven't addressed are the output-sync failures on CentOS Stream. Very strange. I also have no good ideas as to why that is happening.
Re: GNU/Hurd installation
Paul Smith wrote: > > I'll try downloading the 2022-08-24 > > version you reference above and see if that makes a difference. > > It did not matter: same hang. There's clearly some magic pixie dust > that needs to be sprinkled on my system to get this to work, that I do > not have. Unfortunately, this magic pixie dust depends on your CPU model, UEFI/BIOS settings, Linux host kernel version, and VirtualBox version. I've had VMs that became unbootable after moving to a newer hardware, and vice versa. The VirtualBox documentation [1] gives a certain amount of background knowledge, which is then the basis for finding the right setting that makes things work. Sorry, I had expected that it would be as smooth for you as it was for me. Bruno [1] https://www.virtualbox.org/manual/UserManual.html
Re: GNU/Hurd installation
On Sun, 2023-01-15 at 21:31 +0100, Bruno Haible wrote: > In my instructions for GNU/Hurd in 2020 I had noted > Disable 'Nested paging', otherwise it DOES NOT BOOT! > > So, maybe it's worth looking at the main parameters of the VirtualBox VM: > - General: Operating System: Other/Unknown > - System: Motherboard: *Disable* all extended features (I/O APIC, EFI) > - System: Processor: *Disable* all extended features (PAE/NX, Nested VT-x) > [The latter is what I meant above.] > - System: Paravirtualization Interface: You can try different values > than 'Default'. When I choose "Linux 2.4 (32-bit)" as the VM host type, those extended features are disabled by default. However I went through the System setting and turned off anything left such as hardware clock, got rid of the audio card and USB, and I tried a few different paravirtualization interface settings such as Minimal and Legacy but got the same results. > Do you have other VirtualBox VMs that work? Yes, I have other VirtualBox images that work fine.
Re: GNU/Hurd installation
On Sun, 2023-01-15 at 15:06 -0500, Paul Smith wrote: > I did get the "current" version, which was created on 2022-10-30. > Maybe that one is broken? I'll try downloading the 2022-08-24 > version you reference above and see if that makes a difference. It did not matter: same hang. There's clearly some magic pixie dust that needs to be sprinkled on my system to get this to work, that I do not have. I will try the settings that you mentioned in your later email. I will try to start KVM on an IMG file directly to see if that works any better... Well, it worked better in that the image booted and got me to a login: prompt, but I was not successful because it would not accept any keyboard input. I know it was receiving input of some kind because if I moved my mouse around it eventually said "mouse: queue full" so it was getting mouse events.
Re: GNU/Hurd installation
Paul Smith wrote: > I've tried a couple of times, using different instructions (VirtualBox > and vanilla KVM) and every time when it starts to boot the first time > (after selecting this install) it prints: > > ... > module 0: initrd $(ramdisk-create) > rd0: 13279232 bytes @fa491 > module 1: ext2fs ... > module 2: exec $(exec-task=task-create) > 3 multiboot modules > task loaded: ext2fs ... > zip:device:rd0 > task loaded: exec > > start ext2fs: _ > > and hangs there. In my instructions for GNU/Hurd in 2020 I had noted Disable 'Nested paging', otherwise it DOES NOT BOOT! So, maybe it's worth looking at the main parameters of the VirtualBox VM: - General: Operating System: Other/Unknown - System: Motherboard: *Disable* all extended features (I/O APIC, EFI) - System: Processor: *Disable* all extended features (PAE/NX, Nested VT-x) [The latter is what I meant above.] - System: Paravirtualization Interface: You can try different values than 'Default'. Do you have other VirtualBox VMs that work? If not, i.e. if you get problems also with other OSes as guests, I would verify that VT-x/AMD-V is enabled in the UEFI/BIOS. Bruno
Re: GNU/Hurd installation
On Sun, Jan 15, 2023 at 3:04 PM Paul Smith wrote: > > On Sun, 2023-01-15 at 19:24 +0100, Bruno Haible wrote: > > Pseudo-graphical install. > > I've tried a couple of times, using different instructions (VirtualBox > and vanilla KVM) and every time when it starts to boot the first time > (after selecting this install) it prints: > > ... > module 0: initrd $(ramdisk-create) > rd0: 13279232 bytes @fa491 > module 1: ext2fs ... > module 2: exec $(exec-task=task-create) > 3 multiboot modules > task loaded: ext2fs ... > zip:device:rd0 > task loaded: exec > > start ext2fs: _ > > and hangs there. No files appear to be updated on my disk in the > VirtualBox directory. The first time I got a "program appears to be > unresponsive" after a few minutes, and killed it. > > It has already been hung for >10 minutes but I will let it go longer to > see what happens. Installation of Hurd has been failing for me since 2019. I think Samuel is overworked, and he could use a hand at times. See https://lists.debian.org/debian-hurd/2019/02/msg3.html . Jeff
Re: GNU/Hurd installation
On Sun, 2023-01-15 at 19:24 +0100, Bruno Haible wrote: > Download > https://cdimage.debian.org/cdimage/ports/latest/hurd-i386/20220824/debian-sid-hurd-i386-DVD-1.iso I did get the "current" version, which was created on 2022-10-30. Maybe that one is broken? I'll try downloading the 2022-08-24 version you reference above and see if that makes a difference. It would be unfortunate if the ISO images have been unbootable for the last 2.5 months and no one noticed... :-/
Re: GNU/Hurd installation
On Sun, 2023-01-15 at 19:24 +0100, Bruno Haible wrote: > Pseudo-graphical install. I've tried a couple of times, using different instructions (VirtualBox and vanilla KVM) and every time when it starts to boot the first time (after selecting this install) it prints: ... module 0: initrd $(ramdisk-create) rd0: 13279232 bytes @fa491 module 1: ext2fs ... module 2: exec $(exec-task=task-create) 3 multiboot modules task loaded: ext2fs ... zip:device:rd0 task loaded: exec start ext2fs: _ and hangs there. No files appear to be updated on my disk in the VirtualBox directory. The first time I got a "program appears to be unresponsive" after a few minutes, and killed it. It has already been hung for >10 minutes but I will let it go longer to see what happens.
Re: GNU/Hurd installation
Paul Smith wrote: > I will download a GNU/Hurd KVM image, as suggested here: > > https://www.debian.org/ports/hurd/hurd-cd > > is that appropriate for testing? Yes. The GNU/Hurd installation instructions vary a bit over time, but these are my notes from 5 months ago. Fill in the ** fields. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Download https://cdimage.debian.org/cdimage/ports/latest/hurd-i386/20220824/debian-sid-hurd-i386-DVD-1.iso Start VirtualBox. Create new VM. Disk size: 8 GB Pseudo-graphical install. Language: English Location: United States Keymap: American English Hostname: ** Domain name: ** No root account. login: ** password: ** Accept a dummy time zone. Partitioning: Entire disk. All files in one partition. Software selection: Debian desktop environment. (Well, that was not necessary, as I didn't really get the desktop running later.) Reboot. Eject CD-ROM. Set time zone: sudo dpkg-reconfigure tzdata Install packages: Insert CD-ROM, boot, "Boot from first hard disk". $ sudo apt install g++-12 gdb make vim $ sudo apt install emacs # not available Package list for further packages: https://packages.debian.org/en/sid/
