Hmmm...when I start with -boot d, I get exactly the same output...
-Nick
Igor Kovalenko 06/03/10 2:12 PM >>>
On Thu, Jun 3, 2010 at 6:06 PM, Nick Couchman wrote:
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?
That's a bug. Adding "-boot d" to command line helps getting a bit further, whereas in fact there should be no difference between that and "boot cdrom"