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: Sun, 26 Oct 2025 11:19:41 +0530	[thread overview]
Message-ID: <CAJOT6qN4QYRdNR-oQV8JSv_074umiHB==_dyemX01+FsNiqPOQ@mail.gmail.com> (raw)
In-Reply-To: <a410ac54-d1dc-aa67-d1d7-690b2495e9df@eik.bme.hu>

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

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.

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

yogi@fedora:~/work/images$ file debian-8.11.0-powerpc-netinst.iso
debian-8.11.0-powerpc-netinst.iso: ISO 9660 CD-ROM filesystem data (DOS/MBR
boot sector) 'Debian 8.11.0 ppc 1'

Qemu distro version:
yogi@fedora:~/work/images$ qemu-system-ppc --version
QEMU emulator version 9.2.4 (qemu-9.2.4-2.fc42)
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers
yogi@fedora:~/work/images$ qemu-system-ppc64 --version
QEMU emulator version 9.2.4 (qemu-9.2.4-2.fc42)
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers

When using upstream Qemu (both ppc and pp64) with VOF it just gets stuck
with no console output. Am I missing something?

I also tried applying the patches from
https://lore.kernel.org/qemu-devel/cover.1761346145.git.balaton@eik.bme.hu/T/#t
but still the same issue.

Regards,
Yogesh



> Regards,
> BALATON Zoltan
>

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

  reply	other threads:[~2025-10-26  5:51 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 [this message]
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
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='CAJOT6qN4QYRdNR-oQV8JSv_074umiHB==_dyemX01+FsNiqPOQ@mail.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).