All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Aniket Sahu <asahu1x@linux.ibm.com>
Cc: qemu-devel@nongnu.org,  qemu-ppc@nongnu.org,  peterx@redhat.com,
	farosas@suse.de,  npiggin@gmail.com,  adityag@linux.ibm.com,
	milesg@linux.ibm.com,  harshpb@linux.ibm.com,
	 rathc@linux.ibm.com, anushree.mathur@linux.ibm.com,
	 misanjum@linux.ibm.com, gautam@linux.ibm.com,  thuth@redhat.com,
	 amachhiw@linux.ibm.com
Subject: Re: [PATCH 0/5] tests/functional/ppc64: Fixes and improvements for hypervisor tests
Date: Fri, 20 Nov 2026 16:06:06 +0000	[thread overview]
Message-ID: <87y0an4he9.fsf@draig.linaro.org> (raw)
In-Reply-To: <20261120095854.35941-7-asahu1x@linux.ibm.com> (Aniket Sahu's message of "Fri, 20 Nov 2026 15:28:53 +0530")

Aniket Sahu <asahu1x@linux.ibm.com> writes:

> This series fixes several issues in the PPC64 hypervisor functional tests
> and improves their robustness and reliability.

Just a quick note to say the power hardware we have from OSUL doesn't
expose a hypervisor so we can't currently run these tests in the
upstream CI. Do you know of any way we could get such hardware added to
the CI?

Also I should note it would be nice to get:

  https://gitlab.com/qemu-project/qemu/-/work_items/3207

addressed. Let me know if you need access to the system.

>
> Changes in this series:
> -----------------------
>
> 1. Replace deprecated datetime.utcnow() with datetime.now(timezone.utc)
>    to avoid deprecation warnings in Python 3.12+.
>
> 2. Pin machine types to avoid CPU compatibility issues between the L0
>    QEMU (which now defaults to power11) and the L1 Alpine guest's
>    packaged QEMU (which doesn't recognize power11). This fixes
>    "Register sync failed" errors in L2.
>
> 3. Add kernel command line parameters (console=hvc0 usbcore.nousb) and
>    early panic detection to fail fast when L2 encounters issues, plus
>    retry logic for apk update to handle transient network failures.
>
> 4. Dynamically resolve the NVMe device path in L1 instead of hardcoding
>    it, as the device name varies by machine type (nvme0n1 vs nvme1n1).
>    Also adds comprehensive debug logging throughout the test flow and
>    writes the L2 launch command to a script to avoid terminal line-wrap
>    issues.
>
> 5. Increase the test timeout from 1000 to 6000 seconds to accommodate
>    the longer runtime due to apk update retries and additional testing.
>
> Testing:
> --------
> All tests pass on our PPC64 test machines running Ubuntu 26.04 in an
> LPAR.
>
> Aniket Sahu (3):
>   tests/functional/ppc64: replace deprecated datetime.utcnow()
>   tests/functional/ppc64: add kernel params and early panic detection
>   tests/functional/ppc64: dynamically resolve NVMe device path
>
> Misbah Anjum N (2):
>   tests/functional/ppc64: pin machine types for hypervisor tests
>   tests/functional/ppc64: increase timeout for hypervisor tests
>
>  tests/functional/ppc64/meson.build |   2 +-
>  tests/functional/ppc64/test_hv.py  | 140 +++++++++++++++++++++++++----
>  2 files changed, 117 insertions(+), 25 deletions(-)

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


      parent reply	other threads:[~2026-11-20 16:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20  9:58 [PATCH 0/5] tests/functional/ppc64: Fixes and improvements for hypervisor tests Aniket Sahu
2026-11-20  9:58 ` [PATCH 1/5] tests/functional/ppc64: replace deprecated datetime.utcnow() Aniket Sahu
2026-11-20  9:58 ` [PATCH 2/5] tests/functional/ppc64: pin machine types for hypervisor tests Aniket Sahu
2026-11-20 10:06   ` Daniel P. Berrangé
2026-11-20 10:29     ` Aniket Sahu
2026-11-20  9:58 ` [PATCH 3/5] tests/functional/ppc64: add kernel params and early panic detection Aniket Sahu
2026-11-20  9:58 ` [PATCH 4/5] tests/functional/ppc64: dynamically resolve NVMe device path Aniket Sahu
2026-11-20  9:58 ` [PATCH 5/5] tests/functional/ppc64: increase timeout for hypervisor tests Aniket Sahu
2026-11-20 16:06 ` Alex Bennée [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=87y0an4he9.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=adityag@linux.ibm.com \
    --cc=amachhiw@linux.ibm.com \
    --cc=anushree.mathur@linux.ibm.com \
    --cc=asahu1x@linux.ibm.com \
    --cc=farosas@suse.de \
    --cc=gautam@linux.ibm.com \
    --cc=harshpb@linux.ibm.com \
    --cc=milesg@linux.ibm.com \
    --cc=misanjum@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=rathc@linux.ibm.com \
    --cc=thuth@redhat.com \
    /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.