On 8/19/19 7:26 PM, Brad Parker wrote:
> Whoops, 3.11.0 does not exist. Went back and did a full bisect. 3.0.0
> works fine, and the breakage starts before 3.0.1 and 3.1.0 was released,
> specifically, with commit 05306935b1ae49107c2dc2f301574dd6c29b6838.
This commit is migration related. Are you trying to restore/launch a
pre-installed image?
John reported "either not install or will not run 95 or 98 at all" but
you report "95 just reboots infinitely after trying to boot from HDD
after the initial setup." which is slighly different.
What host/os/distrib are you using?
What command line are you using to start QEMU?
If you are using migration, I wonder if the following commit might
affect here:
commit 341ba0df4c69269cac839ddbacb2a0ca641a856d
Author: Peter Maydell <peter.mayd...@linaro.org>
Date: Tue Sep 25 17:19:24 2018 +0100
migration/ram.c: Avoid taking address of fields in packed MultiFDInit_t
struct
Taking the address of a field in a packed struct is a bad idea, because
it might not be actually aligned enough for that pointer type (and
thus cause a crash on dereference on some host architectures). Newer
versions of clang warn about this:
Avoid the bug by not using the "modify in place" byteswapping
functions.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1819289
Title:
Windows 95 and Windows 98 will not install or run
Status in QEMU:
New
Bug description:
The last version of QEMU I have been able to run Windows 95 or Windows
98 on was 2.7 or 2.8. Recent versions since then even up to 3.1 will
either not install or will not run 95 or 98 at all. I have tried every
combination of options like isapc or no isapc, cpu pentium or cpu as
486. Tried different memory configurations, but they just don't work
anymore.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1819289/+subscriptions
