Re: x86_64 image fails to start with high ram

[yelninei--- via Bug reports for the GNU Hurd]

Nov 19, 2025, 15:23 by samuel.thiba...@gnu.org:

> yelninei--- via Bug reports for the GNU Hurd, le mer. 19 nov. 2025 15:11:28 
> +0100, a ecrit:
>
>> Trying to run a x86_64 hurd image with qemu and it fails to boot when the -m 
>> option is too high. Something gets stuck after grub, the last message is
>> ext2fs: part:1:device:wd0: Input/output error
>>
>> After reducing the ram to < 3584 the issue goes away.
>>
>> This happens both with images cross compiled with guix and the 
>> debian-hurd-amd64-20250807.img.
>>
>> Is this limitation currently known?
>>
>
> No, we have some buildds with 16GB ram.
>
> Samuel
>


I am invoking qemu with

qemu-system-x86_64 --enable-kvm -m 3584  debian-hurd-amd64-20250807.img -net 
nic -net user,hostfwd=tcp:127.0.0.1:2222-:22

Do I need some extra qemu flags?

After an unclean shutdown the error seems to happen before the 
"FILESYSTEM NOT UNMOUNTED CLEANLY; PLEASE fsck" message as it dies before.

I tried to work back from there but am not yet sure what is failing.