> So looks like there's some further variable involved beyond just the
> glib update - perhaps something about the host OS is combining with
> the glib update to trigger it.
Agreed - I just retested using a Fedora 30 instance on EC2, with
glib2-2.60.1-2.fc30.x86_64, and was also unable to reprod
Doh, sorry for my comment earlier where I mistakenly used sparc instead
of sparc64.
I've now tested QEMU git master with that sparc64 ISO and qemu-system-
sparc64.
I still can't reproduce it though - it boots past the disk probing, and
into the installer, where it asks for the terminal type.
So
> The test image that the netbsd bug points to no longer exists.
Please try this one instead:
https://www.gson.org/bugs/qemu/NetBSD-8.99.47-sparc64.iso
I just verified that this image works for reproducing the bug.
--
You received this bug notification because you are a member of qemu-
devel
> From the netbsd bug report it looks like the reproducer was demoed
> using the sparc emulator - is that the only QEMU arch that is affected ?
Only one arch is affected, but it's sparc64, not sparc.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subsc
The test image that the netbsd bug points to no longer exists.
If I pick the image currently available:
http://nycdn.netbsd.org/pub/NetBSD-
daily/HEAD/latest/images/NetBSD-9.99.2-sparc.iso
And launch it in a QEMU built from today's GIT master, on Fedora 30 with
glib2 2.60.5, NetBSD successfull
Fedora 30 has been shipping glib2 2.60.0 through to 2.60.5 and QEMU in
general has been working normally AFAICT.
>From the netbsd bug report it looks like the reproducer was demoed using
the sparc emulator - is that the only QEMU arch that is affected ?
--
You received this bug notification beca
