[SLOF] Loading file from disk image

[Jd Lyons]

Having trouble with the latest code: Qemu -m pseries -cpu power8
SLOF **********************************************************************
QEMU Starting
 Build Date = Jan  9 2018 16:32:41
 FW Version = git-a523d1b0cd6e96cf
qemu-system-ppc64: Trying to execute code outside RAM or ROM at 0x00000000386364d4
This usually means one of the following happened:

(1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine)
(2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end
(3) Your guest kernel has a bug and crashed by jumping off into nowhere

This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine.
If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point.

Execution cannot continue; stopping here.

LOF **********************************************************************
QEMU Starting
 Build Date = Jan  9 2018 16:32:41
 FW Version = git-a523d1b0cd6e96cf
qemu-system-ppc64: Trying to execute code outside RAM or ROM at 0x00000000386364d4
This usually means one of the following happened:

(1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine)
(2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end
(3) Your guest kernel has a bug and crashed by jumping off into nowhere

This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine.
If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point.

Execution cannot continue; stopping here.


    On Friday, January 5, 2018, 6:21:39 AM EST, Jd Lyons <lyons_dj at yahoo.com> wrote:  
 
 > 
> Doesn’t seem to be a load word in this commit?
> 

Does anyone know where the load word is defined in SLOF source, I can’t seem to find it?

Also, what is the best way to index/search source code on Linux, I keep the code on the macOS as spotlight does an ok job of being able to quickly find most anything I’m looking for.  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/slof/attachments/20180109/a7e55e01/attachment.html>