qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yogesh Vyas <yvyas1991@gmail.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
	Nicholas Piggin <npiggin@gmail.com>,
	Markus Armbruster <armbru@redhat.com>,
	Harsh Prateek Bora <harshpb@linux.ibm.com>
Subject: Re: [PATCH v3 00/13] Pegasos2 clean up and pegasos1 emulation
Date: Mon, 27 Oct 2025 19:54:32 +0530	[thread overview]
Message-ID: <38673ed9-4690-472b-9e0f-c8a736247097@gmail.com> (raw)
In-Reply-To: <993819c9-cf87-ec91-31ac-f8988c8d3d67@eik.bme.hu>

[-- Attachment #1: Type: text/plain, Size: 5176 bytes --]


On 10/26/25 10:15 PM, BALATON Zoltan wrote:
> On Sun, 26 Oct 2025, Yogesh Vyas wrote:
>
>>
>> On 10/26/25 4:39 PM, BALATON Zoltan wrote:
>>> On Sun, 26 Oct 2025, Yogesh Vyas wrote:
>>>> On Sun, Oct 19, 2025 at 5:37 PM BALATON Zoltan <balaton@eik.bme.hu> 
>>>> wrote:
>>>>> On Sun, 19 Oct 2025, Yogesh Vyas wrote:
>>>>>> When I run QEMU with the ROM option, the machine boots 
>>>>>> successfully with
>>>>>> the below command:
>>>>>>
>>>>>> qemu-system-ppc64 -machine pegasos2 -bios pegasos2.rom \
>>>>>>                  -cdrom debian-8.11.0-powerpc-netinst.iso \
>>>>>>                  -device VGA,romfile="" -serial stdio
>>>>>>
>>>>>> However, when I try to boot the machine without the ROM using 
>>>>>> VOF, the
>>>>>> machine does not come up and no logs appear on stdout:
>>>>>>
>>>>>> qemu-system-ppc64 -machine pegasos2 -serial stdio \
>>>>>>                  -kernel vmlinuz-chrp.initrd -append "---" \
>>>>>>                  -cdrom debian-8.11.0-powerpc-netinst.iso
>>>>>>
>>>>>> Please let me know if I am missing any parameters or setup 
>>>>>> required for
>>>>>> booting via VOF on Pegasos2.
>>>>>>
>>>>>> Documentation referred: qemu/docs/system/ppc/amigang.rst
>>>>>
>>>>> Maybe you did not use the right vmlinuz-chrp.initrd. Pegasos2 is a 
>>>>> 32 bit
>>>>> machine so you need /install/powerpc/vmlinuz-chrp.initrd for it 
>>>>> (see in
>>>>> the /install/pegasos script that is used with firmware). Even if 
>>>>> you call
>>>>> it from qemu-system-ppc64 which includes both 32 bit and 64 bit 
>>>>> machines
>>>>> but does not make 32 bit machines 64 bit so you still need the 32 
>>>>> bit OS.
>>>>>
>>>>>
>>>> Hi Balaton,
>>>> I am using 32bit images only and looks like VOF boot works with the 
>>>> distro
>>>> provided Qemu (both ppc and pp64), however doesn't work with 
>>>> upstream Qemu
>>>> for VOF.
>>>
>>> That's odd, it works for me with QEMU master so I can't reproduce this.
>>>
>>>> yogi@fedora:~/work/images$ file vmlinuz-chrp.initrd
>>>> vmlinuz-chrp.initrd: ELF 32-bit MSB executable, PowerPC or cisco 4500,
>>>> version 1 (SYSV), statically linked, not stripped
>>>
>>> The file command says 32-bit for both 
>>> /install/powerpc/vmlinuz-chrp.initrd and 
>>> /install/powerpc64/vmlinuz-chrp.initrd but only the first one should 
>>> work. Can you double check you have the right vmlinuz-chrp.initrd 
>>> file? But if you say the same file works with 9.2.4 I have no idea 
>>> why. I see these files on the CD
>>>
>>>   9301172 Jun 19  2018 /install/powerpc/vmlinuz-chrp.initrd
>>>  10534888 Jun 19  2018 /install/powerpc64/vmlinuz-chrp.initrd
>>
>>
>> I am also using the same file:
>>
>> yogi@fedora:~/work/images$ ls -lrt vmlinuz-chrp.initrd
>> -r--r--r--. 1 yogi yogi 9301172 Oct 18 23:50 vmlinuz-chrp.initrd
>>
>>>
>>> File command says:
>>>
>>> vmlinuz-chrp.initrd:   ELF 32-bit MSB executable, PowerPC or cisco 
>>> 4500, version 1 (SYSV), statically linked, not stripped
>>> vmlinuz-chrp.initrd64: ELF 32-bit MSB executable, PowerPC or cisco 
>>> 4500, version 1 (SYSV), statically linked, not stripped
>>>
>>> but only the first from the powerpc directory is supposed to work 
>>> and it does boot for me with QEMU master. You can also check 
>>> following the other way described in 
>>> qemu/docs/system/ppc/amigang.rst using -bios pegasos2.rom which 
>>> loads the correct image from the CD. Does that work?
>>
>> Yes, I had mentioned it in my first mail that ROM option works as 
>> expected. It is only an issue when using VOF with upstream Qemu.
>
> Or if you suspect it's a VOF issue you can try -trace enable="vof*"
>
Hi Balaton,

As suggested, I tried both options in upstream:
yogi@fedora:~/work/git/fork/qemu/build$ ./qemu-system-ppc -machine 
pegasos2 -serial stdio -kernel ~/work/images/vmlinuz-chrp.initrd -append 
"---" -cdrom ~/work/images/debian-8.11.0-powerpc-netinst.iso -d 
guest_errors -trace enable="vof*"

I could see the below trace and the error message:
  vof_getproplen ph=0x13 "subsystem-vendor-id" => len=4
vof_getprop ph=0x13 "subsystem-vendor-id" => len=4 [00001100]
vof_getproplen ph=0x13 "reg" => len=20
vof_getprop ph=0x13 "reg" => len=20 [00000000 00000000 00000000 00000000 
00000000]
vof_write ih=0x2 [22] "Device tree strings 0x"
vof_write ih=0x2 [8] "01b0d000"
vof_write ih=0x2 [6] " -> 0x"
vof_write ih=0x2 [8] "01b0d405"
vof_write ih=0x2 [2] "
"
vof_write ih=0x2 [22] "Device tree struct  0x"
vof_write ih=0x2 [8] "01b0e000"
vof_write ih=0x2 [6] " -> 0x"
vof_write ih=0x2 [8] "01b0f000"
vof_write ih=0x2 [2] "
"
vof_getprop ph=0x3 "stdin" => len=4 [00000001]
vof_write ih=0x2 [18] "Calling quiesce..."
vof_write ih=0x2 [2] "
"
vof_claimed 0x0..0xd80 size=0xd80
vof_claimed 0x8000..0x10000 size=0x8000
vof_claimed 0x400000..0xcd8dfc size=0x8d8dfc
vof_claimed 0xd00000..0x15a1ec0 size=0x8a1ec0
vof_claimed 0x15a2000..0x1b0b90d size=0x56990d
vof_claimed 0x1b0c000..0x1c0c000 size=0x100000
vof_claimed 0x1ffff000..0x1ffff014 size=0x14
vof_write ih=0x2 [24] "returning from prom_init"
vof_write ih=0x2 [2] "
"
Trying to read invalid spr 1012 (0x3f4) at c0013f48

Regards,

Yogesh Vyas

> Regards,
> BALATON Zoltan

[-- Attachment #2: Type: text/html, Size: 8067 bytes --]

  reply	other threads:[~2025-10-27 14:25 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-18 15:11 [PATCH v3 00/13] Pegasos2 clean up and pegasos1 emulation BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 01/13] ppc/vof: Make nextprop behave more like Open Firmware BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 02/13] hw/ppc/pegasos2: Remove explicit name properties from device tree BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 03/13] hw/ppc/pegasos2: Change device tree generation BALATON Zoltan
2025-10-20  8:47   ` Philippe Mathieu-Daudé
2025-10-20 13:06     ` BALATON Zoltan
2025-10-20 15:04       ` Philippe Mathieu-Daudé
2025-10-20  8:54   ` Philippe Mathieu-Daudé
2025-10-20 13:02     ` BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 04/13] hw/ppc/pegasos2: Remove fdt pointer from machine state BALATON Zoltan
2025-10-20  8:48   ` Philippe Mathieu-Daudé
2025-10-18 15:11 ` [PATCH v3 05/13] hw/ppc/pegasos2: Rename mv field in " BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 06/13] hw/ppc/pegasos2: Add south bridge pointer in the " BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 07/13] hw/ppc/pegasos2: Move PCI IRQ routing setup to a function BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 08/13] hw/ppc/pegasos2: Move hardware specific parts out of machine reset BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 09/13] hw/ppc/pegasos2: Introduce abstract superclass BALATON Zoltan
2025-10-20  8:49   ` Philippe Mathieu-Daudé
2025-10-18 15:11 ` [PATCH v3 10/13] hw/ppc/pegasos2: Add bus frequency to machine state BALATON Zoltan
2025-10-20  8:53   ` Philippe Mathieu-Daudé
2025-10-20 13:26     ` BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 11/13] hw/boards: Extend DEFINE_MACHINE macro to cover more use cases BALATON Zoltan
2025-10-20 15:05   ` Philippe Mathieu-Daudé
2025-10-20 15:11     ` Philippe Mathieu-Daudé
2025-10-20 15:32       ` Philippe Mathieu-Daudé
2025-10-20 15:40         ` BALATON Zoltan
2025-10-20 15:35       ` BALATON Zoltan
2025-10-21  4:47         ` Harsh Prateek Bora
2025-10-18 15:11 ` [PATCH v3 12/13] hw/ppc/pegasos2: Add Pegasos I emulation BALATON Zoltan
2025-10-18 15:11 ` [PATCH v3 13/13] hw/ppc/pegasos2: Add VOF support for pegasos1 BALATON Zoltan
2025-10-19  6:56 ` [PATCH v3 00/13] Pegasos2 clean up and pegasos1 emulation Yogesh Vyas
2025-10-19 12:07   ` BALATON Zoltan
2025-10-26  5:49     ` Yogesh Vyas
2025-10-26 11:09       ` BALATON Zoltan
2025-10-26 13:18         ` Yogesh Vyas
2025-10-26 16:44           ` BALATON Zoltan
2025-10-26 16:45           ` BALATON Zoltan
2025-10-27 14:24             ` Yogesh Vyas [this message]
2025-10-27 20:18               ` BALATON Zoltan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=38673ed9-4690-472b-9e0f-c8a736247097@gmail.com \
    --to=yvyas1991@gmail.com \
    --cc=armbru@redhat.com \
    --cc=balaton@eik.bme.hu \
    --cc=harshpb@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).