[SLOF] Loading file from disk image

Jd Lyons lyons_dj at yahoo.com
Wed Jan 3 02:02:18 AEDT 2018



> On Jan 2, 2018, at 9:25 AM, Thomas Huth <thuth at redhat.com> wrote:
> 
> On 02.01.2018 15:17, Jd Lyons wrote:
>> 
>> 
>>> On Jan 2, 2018, at 8:43 AM, Jd Lyons <lyons_dj at yahoo.com> wrote:
>>> 
>>> Joy!peffpwpc……
>>> 
>>> 14677: [ a5] 0 0 0 2 1 5e77ef40 5e7d1078 4 0 
>>>  14679: [111] encode-int 0 0 2 1 5e77ef40 5e7d1078 4 5e7d107c 4 
>>>  1467b: [112] encode+ 0 0 2 1 5e77ef40 5e7d1078 8 
>>>  1467c: [ 12] b(") 0 0 2 1 5e77ef40 5e7d1078 8 1467e e 
>>>  1468d: [110] property 0 0 2 1 5e77ef40 
>>>  1468f: [127] finish-device 0 0 2 1 5e77ef40 
>>>  14691: [127] finish-device 0 0 2 1 5e77ef40 
>>>  14693: [de0] xde0 0 0 2 1 5e77ef40 
>>>  14694: [  0] end0 0 0 2 1 5e77ef40 
>>> restored fcode@ 5e77ef40 
>>> restored fcode-spread 1 
>>> restored fcode-offset 2 
>>> restored fcode-end 0 
>>> restored ip 0 
>>> ok
>>> 0 > dev /pci ls  
>>> 5e72ad60 :  /pci at 800000020000000
>>> 5e72d2e8 :  |-- ethernet at 0
>>> 5e72d9d8 :  +-- NVDA,Parent at 1
>>> 5e7cfab0 :      |-- 
>>> 
>> 
>> Seems to be having trouble populating the children,
>> 
>> I should see:
>> 
>>> 5e72d9d8 :  +-- NVDA,Parent at 1
>>> 5e7cfab0 :      |-- NVDA,Display-A
> 
> Indeed, sounds like there is something wrong here. Does SLOF hang during
> the "ls" or do you get back to the firmware prompt? Could you please
> paste the whole log, right from the start of booting the VM?
> 

Seems to scroll on forever after the ls command, so there is some data in the child, not sure what it is. I may try and let it run to it’s end, I only gave it about 10 min.



> Not sure, but in case you've manually started the FCODE from the
> firmware prompt, maybe you've also got to open the node for "extension"
> instead. So instead of doing select-dev or open-dev, could you please
> try this instead:
> 
> dev /pci/vga
> get-node extend-device
> 

Seems to matter the oder I do things, I haven’t figured the correct oder of commands:

qemu-system-ppc64: vfio/eeh: EEH_PE_OP 0x1 failed: Inappropriate ioctl for device


SLOF **********************************************************************
QEMU Starting
 Build Date = Jul 24 2017 15:15:46
 FW Version = git-89f519f09bf85091
 Press "s" to enter Open Firmware.

Populating /vdevice methods
Populating /vdevice/vty at 71000000
Populating /vdevice/nvram at 71000001
Populating /vdevice/v-scsi at 71000002
       SCSI: Looking for devices
          8000000000000000 DISK     : "QEMU     QEMU HARDDISK    2.5+"
          8100000000000000 DISK     : "QEMU     QEMU HARDDISK    2.5+"
          8200000000000000 CD-ROM   : "QEMU     QEMU CD-ROM      2.5+"
Populating /pci at 800000020000000
                     00 0000 (D) : 10ec 8139    network [ ethernet ]
                     00 0800 (D) : 10de 0141    vga*
Scanning USB 
Using default console: /vdevice/vty at 71000000
     
  Welcome to Open Firmware

  Copyright (c) 2004, 2017 IBM Corporation All rights reserved.
  This program and the accompanying materials are made available
  under the terms of the BSD License available at
  http://www.opensource.org/licenses/bsd-license.php


  Type 'boot' and press return to continue booting the system.
  Type 'reset-all' and press return to reboot the system.


Ready! 
0 > dev /pci/vga   ok
0 > get-node extend-device   ok
0 > include evaluator.fs   ok
0 > load disk1:,\666  
Trying to load:  from: /vdevice/v-scsi at 71000002/disk at 8100000000000000:,\666 ...  ok
0 > 4040 1 byte-load   no current instance
0 > s" /pci/vga" select-dev   ok
0 > load disk1:,\666  
Trying to load:  from: /vdevice/v-scsi at 71000002/disk at 8100000000000000:,\666 ...  ok
0 > 4040 1 byte-load   byte-load Undefined word

0 > 4040 1 byte-load   byte-load Undefined word

0 > include evaluator.fs   ok
0 > 4040 1 byte-load   FCode called abort: IP 1405f 6 b 
 Aborted
0 > true to eva-debug?   ok
0 > 4040 1 byte-load 


> Thomas



More information about the SLOF mailing list