[Qemu-devel] OpenBSD/macppc and sparc64 failing to boot with similar error.

[Brad]

I know sparc64 had little chance of actually working but
I thought I'd take it for a spin with 0.15.0-rc1 and
see how it fared in addition to macppc which has a good
chance of working nowdays with modern QEMU. Lets see
what QEMU and related bugs are left..

I noticed the bootblocks for each respective arch are
failing in a very similar manner. I would guess that
this is most likely a bug with the OpenBIOS Open Firmware
implementation?

Any assistance with this? Blue?


$ qemu-system-ppc -nographic -cdrom cd50.iso -boot d      

>> =============================================================
>> OpenBIOS 1.0 [Jun 16 2011 08:02]
>> Configuration device id QEMU version 1 machine id 2
>> CPUs: 1
>> Memory: 128M
>> UUID: 00000000-0000-0000-0000-000000000000
>> CPU type PowerPC,750
Welcome to OpenBIOS v1.0 built on Jun 16 2011 08:02
Trying cd:,\\:tbxi...
>> OpenBSD/macppc BOOT 1.1
open(cd:/etc/boot.conf): Unknown error: code 24
boot> ?


$ qemu-system-sparc64 -nographic -cdrom cd50.iso -boot d
OpenBIOS for Sparc64
Configuration device id QEMU version 1 machine id 0
kernel cmdline 
CPUs: 1 x SUNW,UltraSPARC-IIi
UUID: 00000000-0000-0000-0000-000000000000
Welcome to OpenBIOS v1.0 built on Jul 20 2011 21:17
  Type 'help' for detailed information
Trying cdrom:f...
Not a bootable ELF image
Not a bootable a.out image

Loading FCode image...
Loaded 4829 bytes
entry point is 0x4000
OpenBSD IEEE 1275 Bootblock 1.3
..
Jumping to entry point 0000000000100000 for type 0000000000000001...
switching to new context: entry point 0x100000 stack 0x00000000ffe86b49
>> OpenBSD BOOT 1.4
Trying bsd...
open 
????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????:
 Unknown error: code 24

Boot:

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.