From: Cornelia Huck <cohuck@redhat.com>
To: Matthew Rosato <mjrosato@linux.ibm.com>,
Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Subject: Re: [PULL 00/11] 11.1 compat machines and s390x updates
Date: Fri, 24 Apr 2026 09:47:07 +0200 [thread overview]
Message-ID: <87se8kssuc.fsf@redhat.com> (raw)
In-Reply-To: <9ff8cb74-8abc-4c9a-8f25-044cd4b9d921@linux.ibm.com>
On Thu, Apr 23 2026, Matthew Rosato <mjrosato@linux.ibm.com> wrote:
> On 4/23/26 7:20 PM, Stefan Hajnoczi wrote:
>> On Thu, Apr 23, 2026 at 5:50 AM Cornelia Huck <cohuck@redhat.com> wrote:
>>
>>> The following changes since commit
>>> 98b060da3a4f92b2a994ead5b16a87e783baf77c:
>>>
>>> Update version for v11.0.0 release (2026-04-21 16:28:47 +0100)
>>>
>>> are available in the Git repository at:
>>>
>>> https://gitlab.com/cohuck/qemu tags/s390x-20260423
>>>
>>> for you to fetch changes up to 83f5164d25634f9104b5fb4a6772766ae646ad59:
>>>
>>> hw/s390x/ccw: Disable legacy virtio-pci by default (v11.1+) (2026-04-22
>>> 11:28:03 +0200)
>>>
>>> ----------------------------------------------------------------
>>> First batch of updates for 11.1:
>>> - compat machines for 11.1
>>> - s390x: simplifications, cleanups, and a new test
>>>
>>
>> Hi Cornelia,
>> There is an s390x timeout regression in this pull request that reproduces
>> both in the CI and locally:
>>
>> $ make check-functional-s390x
>> 13/13 qemu:func-thorough+func-s390x-thorough+thorough /
>> func-s390x-ccw_virtio TIMEOUT 420.07s killed by signal 15
>> SIGTERM
>
>
> Hi Connie, it looks to me like the failure is due to disabling legacy
> virtio-pci by default for s390x starting with 11.1.
Duh, I thought I did run all tests, but apparently not.
>
> I was able to get the test to pass again with the diff below. But
> wasn't sure, do we only care about the default/latest machine version
> for functional tests?
>
> diff --git a/tests/functional/s390x/test_ccw_virtio.py b/tests/functional/s390x/test_ccw_virtio.py
> index 0455337856..1d4958bbe2 100755
> --- a/tests/functional/s390x/test_ccw_virtio.py
> +++ b/tests/functional/s390x/test_ccw_virtio.py
> @@ -136,7 +136,7 @@ def test_s390x_devices(self):
> r'0x1af4')
> exec_command_and_wait_for_pattern(self,
> r'cat /sys/bus/pci/devices/0005\:00\:00.0/subsystem_device',
> - r'0x0001')
> + r'0x1100')
> # check fid propagation
> exec_command_and_wait_for_pattern(self,
> r'cat /sys/bus/pci/devices/000a\:00\:00.0/function_id',
> @@ -203,7 +203,7 @@ def test_s390x_fedora(self):
> 'while ! (dmesg | grep enP7p0s0) ; do sleep 1 ; done',
> 'virtio_net virtio0 enP7p0s0: renamed')
> exec_command_and_wait_for_pattern(self, 'lspci',
> - '0007:00:00.0 Class 0200: Device 1af4:1000')
> + '0007:00:00.0 Class 0200: Device 1af4:1041')
> exec_command_and_wait_for_pattern(self,
> 'cat /sys/class/net/enP7p0s0/address',
> '02:ca:fe:fa:ce:12')
AFAICS we always run with the default (latest) machine, so adapting to
any changed output there is probably the way to go -- unless we want to
test various permutations of older machines, but I think that would get
out of hand pretty quickly.
Can you send this with proper tags, I'll just go ahead and merge it.
prev parent reply other threads:[~2026-04-24 7:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 9:48 [PULL 00/11] 11.1 compat machines and s390x updates Cornelia Huck
2026-04-23 9:48 ` [PULL 01/11] target/s390x/kvm: Simplify the async pfault handling code Cornelia Huck
2026-04-23 9:48 ` [PULL 02/11] target/s390x: Replace legacy ld/st_phys -> address_space_ld/st (cpu) Cornelia Huck
2026-04-23 9:48 ` [PULL 03/11] target/s390x: Replace legacy ld/st_phys -> address_space_ld/st (mmu) Cornelia Huck
2026-04-23 9:48 ` [PULL 04/11] target/s390x: Replace legacy ld/st_phys -> address_space_ld/st (tcg) Cornelia Huck
2026-04-23 9:48 ` [PULL 05/11] target/s390x: Replace legacy ld/st_phys -> address_space_ld/st (kvm) Cornelia Huck
2026-04-23 9:48 ` [PULL 06/11] configs/targets: Restrict the legacy ldst_phys() API on s390x target Cornelia Huck
2026-04-23 9:48 ` [PULL 07/11] tests/functional/s390x: Add test for booting from a disk with 4k sectors Cornelia Huck
2026-04-23 9:48 ` [PULL 08/11] hw: add compat machines for 11.1 Cornelia Huck
2026-04-23 9:48 ` [PULL 09/11] target/s390x: Prefer MO_128 definition over magic value Cornelia Huck
2026-04-23 9:48 ` [PULL 10/11] MAINTAINERS: Update s390 trees Cornelia Huck
2026-04-23 9:48 ` [PULL 11/11] hw/s390x/ccw: Disable legacy virtio-pci by default (v11.1+) Cornelia Huck
2026-04-23 23:20 ` [PULL 00/11] 11.1 compat machines and s390x updates Stefan Hajnoczi
2026-04-24 0:44 ` Matthew Rosato
2026-04-24 7:47 ` Cornelia Huck [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=87se8kssuc.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=mjrosato@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=stefanha@gmail.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.