Thomas,
On 20/11/2025 08:46, Thomas Schweikle wrote:
On Thu, Nov 20, 2025 at 9:14 AM Michael Kelly <[email protected]>
wrote:
I've been involved in some recent changes in this area but cannot
reproduce what you experience. Are you referring to the
'debian-hurd-amd64-20251105.img.tar.xz' image, for example?
Yes. Or the others:
debian-hurd{,-amd64,-amd64-20250807}.img{.gz,.tar.gz,.tar.xz,.zip,}
If you also see these problems in 20250807 images then the problem does
not relate to recent interrupt code changes as I supposed.
unpacked they are all the same. And
debian-hurd-2025-amd64-NETINST-1.iso
Tried the i386-images too, but with same results.
Can you present the qemu configuration that you are using so that
I can attempt to reproduce?
Here it is:
/usr/bin/qemu-system-x86_64 -name guest=dhu,debug-threads=on -S \
-object
{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-11-dhu/master-key.aes"}
\
-machine
pc-q35-5.0,usb=off,vmport=off,dump-guest-core=off,memory-backend=pc.ram,hpet=off,acpi=on
-accel kvm \
What software are you using to produce this qemu invocation? I am unable
to generate a virtual machine with the deprecated machine type of
'pc-q35-5.0' so have no way of knowing if this is contributing to these
issues. Presumably your qemu version is 9.2.1 but that doesn't match
with this machine type either.
Regards,
Mike.
