Greetings -
I'm using qemu-system-i386 to try and boot a guest using the NeXTSTEP
3.3 OS on the VM. Unfortunately, the SCSI controller options are very
limited and the 53c810 is the one I have had the best success with. Even
more unfortunately, it seems you cannot boot from it. I'm running qemu
9.0.2 on Arch Linux on an x86_64 host with SeaBIOS 1.16.3-1 using the
following command:
qemu-system-i386 \
-monitor stdio \
-machine pc-i440fx-9.0 \
-cpu pentium2 \
-boot menu=on \
-m 256 \
-display gtk \
-device cirrus-vga \
-device lsi53c810,multifunction=on,id=scsi0 \
-device sb16 \
-device tulip,netdev=vmnic \
-netdev tap,id=vmnic,ifname=next0,script=no,downscript=no \
-drive file=ns33.img,id=disk,format=raw,if=none \
-device scsi-hd,drive=disk \
-drive file=NeXTSTEP_3.3_Developer.iso,format=raw,id=instcd,if=none \
-device scsi-cd,drive=instcd
If I boot the machine, and press ESC to get the boot menu, only "Legacy
option rom" and "Floppy [drive A]" exist. Choosing either causes a "No
bootable device." error message. I also tried appending
,romfile=8xx_64.rom to the device using the ROM image from 86Box, no
change (and the ROM doesn't seem to do anything). If I change the
controller to an lsi53c895a then it appears in the menu, and will boot
the disk, but sadly NeXTSTEP 3.3 doesn't recognize that controller.
I'm not sure if this is a SeaBIOS bug, a QEMU bug, or an Arch packaging
bug. But I figured I would provide the steps and start here after
spending hours searching to see if this is a known bug or not.
-Carl
