Re: [Qemu-devel] [Bug 1471904] Re: qemu fails under NeXTStep 3.3 when accessing ROM in SCSI-Adapter am53c974

[BALATON Zoltan]

On Tue, 26 Jun 2018, Uwe Lienig wrote:
> the issue is still reproducible. I'm still eager to run this old beast
> because of an old database application that has not been converted to
> our new platform. There is an old NeXTStep Black Hardware that is
> running the sybase database. The frontend runs under NeXTStep intel.
> Using qemu would allow to remove some old i486 NeXTStep systems.

This reminds me to this:

http://lists.nongnu.org/archive/html/qemu-devel/2012-09/msg00280.html

my reply to a patch submitted on list a few years ago that was needed to 
fix OpenStep (which might be the same for NeXTStep too) but at the end 
after several iterations it was not accepted due to fear that it may break 
backwards migration which was deemed more important than supporting old 
guests at the time. Maybe this could be reconsidered now if it fixes your 
problem or at least you can have a local fix.

The actual patch needed is just this:

http://lists.nongnu.org/archive/html/qemu-devel/2012-12/msg02360.html

from this series:

http://lists.nongnu.org/archive/html/qemu-devel/2012-12/msg02356.html

which is the last version I've found. You can discover the whole story and 
a lot of background info by searching the qemu-devel list archives for 
"Microport UNIX". For KVM, I think another set of patches are needed (or 
one of those patches) that are linked from one of those messages 
somewhere but I don't remember that.

This may not fix your SCSI problems but could be relevant to the other IDE 
bug mentioned in this bug but it was easier to reply to this email than 
trying to log into launchpad. Sorry for the noise if this turns out not to 
be relevant.

Regards,
BALATON Zoltan