[Qemu-devel] [Bug 1819289] Re: Windows 95 and Windows 98 will not install or run

[Brad Parker]

Here is the exact working command line I used for Windows 95C (OSR2.5):

qemu-system-i386 -cpu pentium -m 128 -vga std -no-kvm -hda
~/Win95C.qcow2 -nodefaults -no-hpet -no-acpi -nodefaults -monitor stdio
-sdl -boot menu=on,order=c,splash-time=2000 -accel tcg,thread=single

To install the OS I simply added -cdrom and -fda, but everything else
stayed the same.

This was using the latest master (33f18cf, after v4.1.0) and its
included bios binaries.

-- 
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

[Qemu-devel] [Bug 1819289] Re: Windows 95 and Windows 98 will not install or run

[Brad Parker]

I tried reverting that commit on top of master but it did not help, so
I'm guessing it broke yet again (differently) somewhere else. I'll try
reverting cd1bfd5 on top of the very next commit and bisect from there
to master, and see where that takes me.

-- 
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

[Qemu-devel] [Bug 1819289] Re: Windows 95 and Windows 98 will not install or run

[Brad Parker]

Just finished a bisect between cfcca36 (working) and current master (not
working), here is the result:

$ git bisect bad
cd1bfd5ef336166b275a09dc9842542bf5e63ae3 is the first bad commit
commit cd1bfd5ef336166b275a09dc9842542bf5e63ae3
Author: Gerd Hoffmann 
Date:   Wed Jun 20 12:17:34 2018 +0200

seabios: update bios and vgabios binaries

Adds two new vgabios binaries, for ramfb and bochs-display.

Signed-off-by: Gerd Hoffmann 

 pc-bios/bios-256k.bin | Bin 262144 -> 262144 bytes
 pc-bios/bios.bin  | Bin 131072 -> 131072 bytes
 pc-bios/vgabios-bochs-display.bin | Bin 0 -> 27648 bytes
 pc-bios/vgabios-cirrus.bin| Bin 38400 -> 38400 bytes
 pc-bios/vgabios-qxl.bin   | Bin 38912 -> 38912 bytes
 pc-bios/vgabios-ramfb.bin | Bin 0 -> 28160 bytes
 pc-bios/vgabios-stdvga.bin| Bin 38912 -> 38912 bytes
 pc-bios/vgabios-virtio.bin| Bin 38912 -> 38912 bytes
 pc-bios/vgabios-vmware.bin| Bin 38912 -> 38912 bytes
 pc-bios/vgabios.bin   | Bin 38400 -> 38400 bytes
 10 files changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 pc-bios/vgabios-bochs-display.bin
 create mode 100644 pc-bios/vgabios-ramfb.bin

-- 
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

[Qemu-devel] [Bug 1819289] Re: Windows 95 and Windows 98 will not install or run

[Brad Parker]

So it looks like even though that commit fixed it, it seems to break
again (differently) in 3.0.0, so I'll need to do another bisect between
cfcca36 and v3.0.0 then I guess. And keep working my way up to master as
well.

-- 
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

[Qemu-devel] [Bug 1819289] Re: Windows 95 and Windows 98 will not install or run

[Brad Parker]

e3af7c788b73a6495 was indeed one of the bad commits I tested during the
bisect. If I apply cfcca361d77142f25f on top of it, Windows starts up
normally instead of giving me a BSOD on bootup.

-- 
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

[Qemu-devel] [Bug 1819289] Re: Windows 95 and Windows 98 will not install or run

[Brad Parker]

Hopefully third time's the charm. I ran yet another bisect, between
2.5.0 (working) and 2.11.0 (not working), this time reinstalling the
entire OS from scratch with a blank disk every single time. Results:

$ git bisect good
e3af7c788b73a6495eb9d94992ef11f6ad6f3c56 is the first bad commit
commit e3af7c788b73a6495eb9d94992ef11f6ad6f3c56
Author: Paolo Bonzini 
Date:   Wed Apr 26 13:59:34 2017 +0200

target/i386: introduce x86_ld*_code

These take care of advancing s->pc, and will provide a unified point
where to check for the 15-byte instruction length limit.

Signed-off-by: Paolo Bonzini 

 target/i386/translate.c | 228 ++--
 1 file changed, 125 insertions(+), 103 deletions(-)

-- 
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

[Qemu-devel] [Bug 1819289] Re: Windows 95 and Windows 98 will not install or run

[Brad Parker]

Just FYI that was the second bisect I had to do, the first time it
produced an even more unrelated commit, so I assumed I must have done
something wrong... apparently that is still the case. After trying the
"working" commit outside of the Docker container, it now does not
work... so I'm at a loss as to how to reliably bisect I guess. Never had
any issues with other projects doing it though.

-- 
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

[Qemu-devel] [Bug 1819289] Re: Windows 95 and Windows 98 will not install or run

[Brad Parker]

I am not using anything related to migration, just launching with a
simple flat qcow2 file, no snapshots, backing stores or anything like
that.

The host is Archlinux x64 but I'm running inside of a docker container
that runs Ubuntu 18.04.

The command-line is:

qemu-system-i386 -spice port=5800,disable-ticketing=on -cpu pentium -m
128 -vga std -no-kvm -hda Win95C.qcow2 -nodefaults -no-hpet -no-acpi
-cdrom Win95C.iso -nodefaults -M isapc -monitor stdio

-- 
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

[Qemu-devel] [Bug 1819289] Re: Windows 95 and Windows 98 will not install or run

[Brad Parker]

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.

-- 
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

[Qemu-devel] [Bug 1819289] Re: Windows 95 and Windows 98 will not install or run

[Brad Parker]

I was able to get both running on 3.11.0, but something broke again by
the time I re-tested on 4.0.0. 98 seems to work on 4.0 at least, but 95
just reboots infinitely after trying to boot from HDD after the initial
setup. I tried searching their mailing list and asking around but nobody
seems interested in fixing it.

-- 
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

[Qemu-devel] [Bug 1715715] Re: [qemu-ppc] Segfault when booting from HD after MacOS9 install

[Brad Parker]

I just tried the latest git and it actually boots fine with your
command... so I guess whatever issue I was having (the null dereference
in the timer code I pasted above) must have been fixed... however I've
noticed another issue with a different command that causes the bootup to
hang:

qemu-system-ppc -boot c -g 1024x768x32 -M mac99 -m 256 -prom-env 'auto-
boot?=true' -prom-env 'boot-args=-v' -prom-env 'vga-ndrv?=true' -drive
file=os9.2.1.iso,format=raw,media=cdrom -drive
file=os921.qcow2,format=qcow2,media=disk -spice port=5901,password=XXX
-net nic,model=sungem -net user -monitor stdio

This hangs at bootup at "Trying hd:,\\:tbxi" and never progresses any
further. If I remove the cdrom then it boots fine... however, simply
adding the cdrom to your working command, it still works there... not
sure what's going on, but thanks for the help. I have something that
works now.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1715715

Title:
  [qemu-ppc] Segfault when booting from HD after MacOS9 install

Status in QEMU:
  New

Bug description:
  I created an empty 128G qcow2 image and booted from a Mac OS 9.2.1
  Install CD, in which I was able to install the OS successfully to the
  hard drive. Upon reboot, this time from the hard drive directly, qemu-
  system-ppc segfaults. Host system is Ubuntu 16.04.2 with latest qemu
  commit.

  qemu --version reports "2.10.50 (v2.10.0-244-gb07d1c2-dirty)", but I
  used git commit b07d1c2f5607489d4d4a6a65ce36a3e896ac065e and built
  with "./configure --target-list=ppc-softmmu --enable-debug --disable-
  strip".

  Here is the command-line arguments:

  qemu-system-ppc -boot c -g 1024x768x32 -M mac99 -m 256 -prom-env
  'auto-boot?=true' -prom-env 'boot-args=-v' -prom-env 'vga-ndrv?=true'
  -drive file=../os9.img,format=raw,media=cdrom -drive
  file=MacOS9.qcow2,format=qcow2,media=disk -spice
  port=5901,password=XXX -net nic,model=rtl8139 -net user -monitor stdio

  And the GDB backtrace:

  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x559065fe7d3a in timer_mod (ts=0x0, expire_time=888960717010) at 
util/qemu-timer.c:462
  462 timer_mod_ns(ts, expire_time * ts->scale);
  [Current thread is 1 (Thread 0x7f60e43cb700 (LWP 9853))]
  (gdb) bt
  #0  0x559065fe7d3a in timer_mod (ts=0x0, expire_time=888960717010) at 
util/qemu-timer.c:462
  #1  0x559065d63769 in openpic_tmr_set_tmr (tmr=0x5590676fa7e0, val=96, 
enabled=true) at hw/intc/openpic.c:861
  #2  0x559065d63995 in openpic_tmr_write (opaque=0x5590676f71f0, addr=16, 
val=96, len=4) at hw/intc/openpic.c:912
  #3  0x559065b02811 in memory_region_write_accessor (mr=0x5590676f7710, 
addr=32, value=0x7f60e43c7da8, size=4, shift=0, mask=4294967295, attrs=...) at 
/home/bp/qemu/memory.c:529
  #4  0x559065b02a29 in access_with_adjusted_size (addr=32, 
value=0x7f60e43c7da8, size=1, access_size_min=4, access_size_max=4, 
access=0x559065b02727 , mr=0x5590676f7710, 
attrs=...) at /home/bp/qemu/memory.c:595
  #5  0x559065b051eb in memory_region_dispatch_write (mr=0x5590676f7710, 
addr=32, data=96, size=1, attrs=...) at /home/bp/qemu/memory.c:1337
  #6  0x559065aa3a36 in address_space_write_continue (as=0x559067614d90, 
addr=2147750160, attrs=..., buf=0x7f60e43c7ed0 "`_'\310`\177", len=1, addr1=32, 
l=1, mr=0x5590676f7710) at /home/bp/qemu/exec.c:2942
  #7  0x559065aa3b84 in address_space_write (as=0x559067614d90, 
addr=2147750160, attrs=..., buf=0x7f60e43c7ed0 "`_'\310`\177", len=1) at 
/home/bp/qemu/exec.c:2987
  #8  0x559065aa2ec0 in subpage_write (opaque=0x7f60c8275fc0, addr=272, 
value=96, len=1, attrs=...) at /home/bp/qemu/exec.c:2565
  #9  0x559065b02906 in memory_region_write_with_attrs_accessor 
(mr=0x7f60c8275fc0, addr=272, value=0x7f60e43c7fc8, size=1, shift=0, mask=255, 
attrs=...) at /home/bp/qemu/memory.c:555
  #10 0x559065b029d3 in access_with_adjusted_size (addr=272, 
value=0x7f60e43c7fc8, size=1, access_size_min=1, access_size_max=8, 
access=0x559065b02818 , 
mr=0x7f60c8275fc0, attrs=...) at /home/bp/qemu/memory.c:590
  #11 0x559065b0523a in memory_region_dispatch_write (mr=0x7f60c8275fc0, 
addr=272, data=96, size=1, attrs=...) at /home/bp/qemu/memory.c:1344
  #12 0x559065b175db in io_writex (env=0x7f60e43d42a0, 
iotlbentry=0x7f60e43e8130, mmu_idx=3, val=96, addr=2147750160, 
retaddr=140054158295744, size=1) at /home/bp/qemu/accel/tcg/cputlb.c:807
  #13 0x559065b18055 in io_writeb (env=0x7f60e43d42a0, mmu_idx=3, index=65, 
val=96 '`', addr=2147750160, retaddr=140054158295744) at 
/home/bp/qemu/softmmu_template.h:265
  #14 0x559065b181ea in helper_ret_stb_mmu (env=0x7f60e43d42a0, 
addr=2147750160, val=96 '`', oi=3, retaddr=140054158295744) at 
/home/bp/qemu/softmmu_template.h:300
  #15 0x7f60e65ac2c0 in code_gen_buffer ()
  #16 0x559065b1ff26 in cpu_tb_exec (cpu=0x7f60e43cc010, itb=0x7f60e65ac5c0 
) 

[Qemu-devel] [Bug 1715715] Re: [qemu-ppc] Segfault when booting from HD after OS install

[Brad Parker]

** Description changed:

  I created an empty 128G qcow2 image and booted from a Mac OS 9.2.1
  Install CD, in which I was able to install the OS successfully to the
  hard drive. Upon reboot, this time from the hard drive directly, qemu-
- system-ppc segfaults.
+ system-ppc segfaults. Host system is Ubuntu 16.04.2 with latest qemu
+ commit.
  
  qemu --version reports "v2.10.0-244-gb07d1c2-dirty", but I used git
  commit b07d1c2f5607489d4d4a6a65ce36a3e896ac065e and built with
  "./configure --target-list=ppc-softmmu --enable-debug --disable-strip".
  
  Here is the command-line arguments:
  
  qemu-system-ppc -boot c -g 1024x768x32 -M mac99 -m 256 -prom-env 'auto-
  boot?=true' -prom-env 'boot-args=-v' -prom-env 'vga-ndrv?=true' -drive
  file=../os9.img,format=raw,media=cdrom -drive
  file=MacOS9.qcow2,format=qcow2,media=disk -spice port=5901,password=XXX
  -net nic,model=rtl8139 -net user -monitor stdio
  
  And the GDB backtrace:
  
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x559065fe7d3a in timer_mod (ts=0x0, expire_time=888960717010) at 
util/qemu-timer.c:462
  462 timer_mod_ns(ts, expire_time * ts->scale);
  [Current thread is 1 (Thread 0x7f60e43cb700 (LWP 9853))]
  (gdb) bt
  #0  0x559065fe7d3a in timer_mod (ts=0x0, expire_time=888960717010) at 
util/qemu-timer.c:462
  #1  0x559065d63769 in openpic_tmr_set_tmr (tmr=0x5590676fa7e0, val=96, 
enabled=true) at hw/intc/openpic.c:861
  #2  0x559065d63995 in openpic_tmr_write (opaque=0x5590676f71f0, addr=16, 
val=96, len=4) at hw/intc/openpic.c:912
  #3  0x559065b02811 in memory_region_write_accessor (mr=0x5590676f7710, 
addr=32, value=0x7f60e43c7da8, size=4, shift=0, mask=4294967295, attrs=...) at 
/home/bp/qemu/memory.c:529
  #4  0x559065b02a29 in access_with_adjusted_size (addr=32, 
value=0x7f60e43c7da8, size=1, access_size_min=4, access_size_max=4, 
access=0x559065b02727 , mr=0x5590676f7710, 
attrs=...) at /home/bp/qemu/memory.c:595
  #5  0x559065b051eb in memory_region_dispatch_write (mr=0x5590676f7710, 
addr=32, data=96, size=1, attrs=...) at /home/bp/qemu/memory.c:1337
  #6  0x559065aa3a36 in address_space_write_continue (as=0x559067614d90, 
addr=2147750160, attrs=..., buf=0x7f60e43c7ed0 "`_'\310`\177", len=1, addr1=32, 
l=1, mr=0x5590676f7710) at /home/bp/qemu/exec.c:2942
  #7  0x559065aa3b84 in address_space_write (as=0x559067614d90, 
addr=2147750160, attrs=..., buf=0x7f60e43c7ed0 "`_'\310`\177", len=1) at 
/home/bp/qemu/exec.c:2987
  #8  0x559065aa2ec0 in subpage_write (opaque=0x7f60c8275fc0, addr=272, 
value=96, len=1, attrs=...) at /home/bp/qemu/exec.c:2565
  #9  0x559065b02906 in memory_region_write_with_attrs_accessor 
(mr=0x7f60c8275fc0, addr=272, value=0x7f60e43c7fc8, size=1, shift=0, mask=255, 
attrs=...) at /home/bp/qemu/memory.c:555
  #10 0x559065b029d3 in access_with_adjusted_size (addr=272, 
value=0x7f60e43c7fc8, size=1, access_size_min=1, access_size_max=8, 
access=0x559065b02818 , 
mr=0x7f60c8275fc0, attrs=...) at /home/bp/qemu/memory.c:590
  #11 0x559065b0523a in memory_region_dispatch_write (mr=0x7f60c8275fc0, 
addr=272, data=96, size=1, attrs=...) at /home/bp/qemu/memory.c:1344
  #12 0x559065b175db in io_writex (env=0x7f60e43d42a0, 
iotlbentry=0x7f60e43e8130, mmu_idx=3, val=96, addr=2147750160, 
retaddr=140054158295744, size=1) at /home/bp/qemu/accel/tcg/cputlb.c:807
  #13 0x559065b18055 in io_writeb (env=0x7f60e43d42a0, mmu_idx=3, index=65, 
val=96 '`', addr=2147750160, retaddr=140054158295744) at 
/home/bp/qemu/softmmu_template.h:265
  #14 0x559065b181ea in helper_ret_stb_mmu (env=0x7f60e43d42a0, 
addr=2147750160, val=96 '`', oi=3, retaddr=140054158295744) at 
/home/bp/qemu/softmmu_template.h:300
  #15 0x7f60e65ac2c0 in code_gen_buffer ()
  #16 0x559065b1ff26 in cpu_tb_exec (cpu=0x7f60e43cc010, itb=0x7f60e65ac5c0 
) at /home/bp/qemu/accel/tcg/cpu-exec.c:166
  #17 0x559065b20bfd in cpu_loop_exec_tb (cpu=0x7f60e43cc010, 
tb=0x7f60e65ac5c0 , last_tb=0x7f60e43c8678, 
tb_exit=0x7f60e43c8674) at /home/bp/qemu/accel/tcg/cpu-exec.c:578
  #18 0x559065b20eed in cpu_exec (cpu=0x7f60e43cc010) at 
/home/bp/qemu/accel/tcg/cpu-exec.c:676
  #19 0x559065aebc3d in tcg_cpu_exec (cpu=0x7f60e43cc010) at 
/home/bp/qemu/cpus.c:1270
  #20 0x559065aebe64 in qemu_tcg_rr_cpu_thread_fn (arg=0x7f60e43cc010) at 
/home/bp/qemu/cpus.c:1365
  #21 0x7f60f56f06ba in start_thread (arg=0x7f60e43cb700) at 
pthread_create.c:333
  #22 0x7f60f542682d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
  
- 
  Any idea what is going on?

** Description changed:

  I created an empty 128G qcow2 image and booted from a Mac OS 9.2.1
  Install CD, in which I was able to install the OS successfully to the
  hard drive. Upon reboot, this time from the hard drive directly, qemu-
  system-ppc segfaults. Host system is Ubuntu 16.04.2 with latest qemu
  commit.
  
- qemu --version reports 

[Qemu-devel] [Bug 1715715] [NEW] [qemu-ppc] Segfault when booting from HD after OS install

[Brad Parker]

Public bug reported:

I created an empty 128G qcow2 image and booted from a Mac OS 9.2.1
Install CD, in which I was able to install the OS successfully to the
hard drive. Upon reboot, this time from the hard drive directly, qemu-
system-ppc segfaults. Host system is Ubuntu 16.04.2 with latest qemu
commit.

qemu --version reports "2.10.50 (v2.10.0-244-gb07d1c2-dirty)", but I
used git commit b07d1c2f5607489d4d4a6a65ce36a3e896ac065e and built with
"./configure --target-list=ppc-softmmu --enable-debug --disable-strip".

Here is the command-line arguments:

qemu-system-ppc -boot c -g 1024x768x32 -M mac99 -m 256 -prom-env 'auto-
boot?=true' -prom-env 'boot-args=-v' -prom-env 'vga-ndrv?=true' -drive
file=../os9.img,format=raw,media=cdrom -drive
file=MacOS9.qcow2,format=qcow2,media=disk -spice port=5901,password=XXX
-net nic,model=rtl8139 -net user -monitor stdio

And the GDB backtrace:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x559065fe7d3a in timer_mod (ts=0x0, expire_time=888960717010) at 
util/qemu-timer.c:462
462 timer_mod_ns(ts, expire_time * ts->scale);
[Current thread is 1 (Thread 0x7f60e43cb700 (LWP 9853))]
(gdb) bt
#0  0x559065fe7d3a in timer_mod (ts=0x0, expire_time=888960717010) at 
util/qemu-timer.c:462
#1  0x559065d63769 in openpic_tmr_set_tmr (tmr=0x5590676fa7e0, val=96, 
enabled=true) at hw/intc/openpic.c:861
#2  0x559065d63995 in openpic_tmr_write (opaque=0x5590676f71f0, addr=16, 
val=96, len=4) at hw/intc/openpic.c:912
#3  0x559065b02811 in memory_region_write_accessor (mr=0x5590676f7710, 
addr=32, value=0x7f60e43c7da8, size=4, shift=0, mask=4294967295, attrs=...) at 
/home/bp/qemu/memory.c:529
#4  0x559065b02a29 in access_with_adjusted_size (addr=32, 
value=0x7f60e43c7da8, size=1, access_size_min=4, access_size_max=4, 
access=0x559065b02727 , mr=0x5590676f7710, 
attrs=...) at /home/bp/qemu/memory.c:595
#5  0x559065b051eb in memory_region_dispatch_write (mr=0x5590676f7710, 
addr=32, data=96, size=1, attrs=...) at /home/bp/qemu/memory.c:1337
#6  0x559065aa3a36 in address_space_write_continue (as=0x559067614d90, 
addr=2147750160, attrs=..., buf=0x7f60e43c7ed0 "`_'\310`\177", len=1, addr1=32, 
l=1, mr=0x5590676f7710) at /home/bp/qemu/exec.c:2942
#7  0x559065aa3b84 in address_space_write (as=0x559067614d90, 
addr=2147750160, attrs=..., buf=0x7f60e43c7ed0 "`_'\310`\177", len=1) at 
/home/bp/qemu/exec.c:2987
#8  0x559065aa2ec0 in subpage_write (opaque=0x7f60c8275fc0, addr=272, 
value=96, len=1, attrs=...) at /home/bp/qemu/exec.c:2565
#9  0x559065b02906 in memory_region_write_with_attrs_accessor 
(mr=0x7f60c8275fc0, addr=272, value=0x7f60e43c7fc8, size=1, shift=0, mask=255, 
attrs=...) at /home/bp/qemu/memory.c:555
#10 0x559065b029d3 in access_with_adjusted_size (addr=272, 
value=0x7f60e43c7fc8, size=1, access_size_min=1, access_size_max=8, 
access=0x559065b02818 , 
mr=0x7f60c8275fc0, attrs=...) at /home/bp/qemu/memory.c:590
#11 0x559065b0523a in memory_region_dispatch_write (mr=0x7f60c8275fc0, 
addr=272, data=96, size=1, attrs=...) at /home/bp/qemu/memory.c:1344
#12 0x559065b175db in io_writex (env=0x7f60e43d42a0, 
iotlbentry=0x7f60e43e8130, mmu_idx=3, val=96, addr=2147750160, 
retaddr=140054158295744, size=1) at /home/bp/qemu/accel/tcg/cputlb.c:807
#13 0x559065b18055 in io_writeb (env=0x7f60e43d42a0, mmu_idx=3, index=65, 
val=96 '`', addr=2147750160, retaddr=140054158295744) at 
/home/bp/qemu/softmmu_template.h:265
#14 0x559065b181ea in helper_ret_stb_mmu (env=0x7f60e43d42a0, 
addr=2147750160, val=96 '`', oi=3, retaddr=140054158295744) at 
/home/bp/qemu/softmmu_template.h:300
#15 0x7f60e65ac2c0 in code_gen_buffer ()
#16 0x559065b1ff26 in cpu_tb_exec (cpu=0x7f60e43cc010, itb=0x7f60e65ac5c0 
) at /home/bp/qemu/accel/tcg/cpu-exec.c:166
#17 0x559065b20bfd in cpu_loop_exec_tb (cpu=0x7f60e43cc010, 
tb=0x7f60e65ac5c0 , last_tb=0x7f60e43c8678, 
tb_exit=0x7f60e43c8674) at /home/bp/qemu/accel/tcg/cpu-exec.c:578
#18 0x559065b20eed in cpu_exec (cpu=0x7f60e43cc010) at 
/home/bp/qemu/accel/tcg/cpu-exec.c:676
#19 0x559065aebc3d in tcg_cpu_exec (cpu=0x7f60e43cc010) at 
/home/bp/qemu/cpus.c:1270
#20 0x559065aebe64 in qemu_tcg_rr_cpu_thread_fn (arg=0x7f60e43cc010) at 
/home/bp/qemu/cpus.c:1365
#21 0x7f60f56f06ba in start_thread (arg=0x7f60e43cb700) at 
pthread_create.c:333
#22 0x7f60f542682d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Any idea what is going on?

** Affects: qemu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1715715

Title:
  [qemu-ppc] Segfault when booting from HD after OS install

Status in QEMU:
  New

Bug description:
  I created an empty 128G qcow2 image and booted from a Mac OS 9.2.1
  Install CD, in which I was able to install the OS successfully to the