From: "Cédric Le Goater" <clg@redhat.com>
To: Aditya Gupta <adityag@linux.ibm.com>
Cc: Nicholas Piggin <npiggin@gmail.com>,
Harsh Prateek Bora <harshpb@linux.ibm.com>,
Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [PATCH v9 0/7] Power11 support for QEMU [PowerNV]
Date: Mon, 11 Aug 2025 14:16:26 +0200 [thread overview]
Message-ID: <90e4fbed-a763-4f02-9752-210bf49d3970@redhat.com> (raw)
In-Reply-To: <yo6uk5z6dlq4jlk5hsaoyhymozdpo6ijpq5bz4fipkf5ftws4b@um57vsttgf65>
On 8/10/25 08:56, Aditya Gupta wrote:
> Hi Cedric,
> Sorry for the late reply, I am on vacation this week, will try to look
> at this, but reply might be late.
>
> On 25/08/08 02:32PM, Cédric Le Goater wrote:
>> On 8/8/25 13:59, Aditya Gupta wrote:
>>> Overview
>>> ============
>>>
>>> Add support for Power11 powernv machine type.
>>>
>>>> <...snip...>
>>
>> Booting a PowerNV11 machine crashes QEMU. See below.
>>
>> Are you testing with petitboot kexecing a distro kernel from disk ?
>> Please do and also start a KVM guest. Please check your tests.
>
> No, I ran the qemu functional tests, and few boot tests with different
> options.
>
> The functional test already attaches a e1000e device, somehow that
> didn't trigger the same error that you saw (maybe the kernel used
> doesn't have support for that device).
> Will add a test to try petitboot kexec scenario also, so we don't hit
> these kind of issues in future.
I run a multi socket config :
qemu-system-ppc64 -m 4G -machine powernv11 -smp 16,sockets=2,cores=2,threads=4 -accel tcg,thread=multi
-kernel ./zImage.epapr
-initrd ./rootfs.cpio.xz
-device pcie-pci-bridge,id=bridge1,bus=pcie.1,addr=0x0 -device nvme,bus=pcie.0,addr=0x0,drive=drive0,serial=1234
-drive file=./Fedora-Cloud-Base-Generic-42-1.1.ppc64le.qcow2,if=none,id=drive0,format=qcow2,cache=none
-device e1000e,netdev=net0,mac=C0:FF:EE:00:01:05,bus=bridge1,addr=0x3
-netdev bridge,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=net0
-device nec-usb-xhci,bus=bridge1,addr=0x2
-device usb-storage,drive=usbkey
-drive file=usb.img,if=none,id=usbkey,format=raw,cache=none
-serial mon:stdio -nographic
See :
https://lore.kernel.org/qemu-devel/3b1fcc0a-6ce7-4639-a17c-34d640745c20@redhat.com/
>
> Regarding KVM guest, iirc we can't start KVM guest for PowerNV yet right
> ?
The QEMU PowerNV machines support emulated KVM guests. XIVE
is a key component in its support, as it controls the wake-up
of the virtual processors.
The QEMU pseries machines support nested too, both implementations:
the initial on OPAL systems and the most recent v2 one for pHyp.
I believe QEMU PowerNV machines support nested KVM too. Never
tried that though.
C.
prev parent reply other threads:[~2025-08-11 12:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 11:59 [PATCH v9 0/7] Power11 support for QEMU [PowerNV] Aditya Gupta
2025-08-08 11:59 ` [PATCH v9 1/7] ppc/pnv: Introduce Pnv11Chip Aditya Gupta
2025-08-08 11:59 ` [PATCH v9 2/7] ppc/pnv: Introduce Power11 PowerNV machine Aditya Gupta
2025-08-08 11:59 ` [PATCH v9 3/7] ppc/pnv: Add XIVE2 controller to Power11 Aditya Gupta
2025-08-08 11:59 ` [PATCH v9 4/7] ppc/pnv: Add PHB5 PCIe Host bridge " Aditya Gupta
2025-08-08 11:59 ` [PATCH v9 5/7] ppc/pnv: Add ChipTOD model for Power11 Aditya Gupta
2025-08-08 11:59 ` [PATCH v9 6/7] tests/powernv: Switch to buildroot images instead of op-build Aditya Gupta
2025-08-08 11:59 ` [PATCH v9 7/7] tests/powernv: Add PowerNV test for Power11 Aditya Gupta
2025-08-08 12:32 ` [PATCH v9 0/7] Power11 support for QEMU [PowerNV] Cédric Le Goater
2025-08-10 6:56 ` Aditya Gupta
2025-08-10 10:45 ` Aditya Gupta
2025-08-10 12:46 ` Access to remote XIVE2 units (was Re: [PATCH v9 0/7] Power11 support for QEMU [PowerNV]) Cédric Le Goater
2025-08-11 15:17 ` Miles Glenn
2025-08-20 6:40 ` Aditya Gupta
2025-08-28 12:04 ` Aditya Gupta
2025-08-28 21:49 ` Cédric Le Goater
2025-09-24 12:14 ` Ganesh G R
2025-09-25 6:38 ` Cédric Le Goater
2025-09-25 12:51 ` Aditya Gupta
2025-08-11 12:16 ` Cédric Le Goater [this message]
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=90e4fbed-a763-4f02-9752-210bf49d3970@redhat.com \
--to=clg@redhat.com \
--cc=adityag@linux.ibm.com \
--cc=harshpb@linux.ibm.com \
--cc=maddy@linux.ibm.com \
--cc=mahesh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.