ofmem_claim_phys - out of space - OpenBIOS

3 Jun 2010


      Well, I've followed the traffic on the list quietly for a few months, updating qemu and openbios along the way as things have developed.  I figured I'd throw out the error I'm getting, now, when I try to boot Milax 0.3.2 with qemu-system-sparc64 and see if this is expected, something that's in the works, or something that should be fixed.  I start with the following command:
sparc64-softmmu/qemu-system-sparc64 -hda disk0 -cdrom /misc/iso/Solaris/milax032sparc.iso -bios ../openbios-devel/obj-sparc64/openbios-builtin.elf.nostrip -nographic
and then do a "boot cdrom" at the prompt.  Here's the output (no debugging, verbosity, etc. - just normal output):
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 May 27 2010 20:47
  Type 'help' for detailed information
[sparc64] Booting file 'disk' with parameters ''
Not a bootable ELF image
Not a Linux kernel image
Not a bootable a.out image
Not a bootable FCode image
Not a bootable ELF image
Not a Linux kernel image
Not a bootable a.out image
Not a bootable FCode image
Unsupported image format
0 > boot cdrom 
[sparc64] Booting file 'cdrom' with parameters ''
Not a bootable ELF image
Not a Linux kernel image
Not a bootable a.out image
Loading FCode image...
Loaded 7084 bytes
entry point is 0x4000
Jumping to entry point 0000000000004000 for type 0000000000000010...
Evaluating FCode...
ofmem_claim_phys - out of space (failed request for 0000000000000000 bytes)
Unhandled Exception 0x0000000008000000
PC = 0x00000000ffd1020c NPC = 0x00000000ffd10210
Stopping execution
Any hints?  Any debugging I should turn on to provide more information?  Or is there another Solaris-type O/S I should try?
Thanks!
-Nick
--------
This e-mail may contain confidential and privileged material for the sole use of the intended recipient.  If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information.  In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way.  If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox.  Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.