All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Eric Farman <farman@linux.ibm.com>,
	Hanna Reitz <hreitz@redhat.com>,
	 qemu-block@nongnu.org, qemu-devel@nongnu.org,
	Matthew Rosato <mjrosato@linux.ibm.com>
Subject: Re: [PATCH v3 1/4] iotests/nbd-in-qcow2-chain: use default machine
Date: Fri, 25 Sep 2026 16:01:55 -0500	[thread overview]
Message-ID: <arbg_YqXp3hi49WK@redhat.com> (raw)
In-Reply-To: <arUf7gFJkCuVH0VI@redhat.com>

On Thu, Sep 24, 2026 at 03:04:46PM +0200, Kevin Wolf wrote:
> Am 13.08.2026 um 20:37 hat Eric Farman geschrieben:
> > Some of the NBD tests explicitly specify `-machine q35` which won't work
> > when running against, say, qemu-system-s390x.
> > 
> > The nbd-in-qcow2-chain test runs fine with the default machine on a z16
> > host, so allow it to run in other configurations.
> > 
> > Fixes: 24fd6d75b3 ("iotests: Add coverage of recent NBD qio deadlock fix")
> > Signed-off-by: Eric Farman <farman@linux.ibm.com>
> > ---

> >  
> > -_launch_qemu -machine q35
> > +_launch_qemu
> >  h1=$QEMU_HANDLE
> >  _send_qemu_cmd $QEMU_HANDLE '{"execute": "qmp_capabilities"}' 'return'
> >  _send_qemu_cmd $QEMU_HANDLE '{"execute": "blockdev-add",
> 
> I don't see what the machine type is needed for, so this is probably
> fine.
> 
> Eric (Blake), any specific reason you added the machine type in this
> test case so that removing it might cause a regression?

This would have been copy-and-paste from some other test, and not
something specific to this one.

Reviewed-by: Eric Blake <eblake@redhat.com>

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization:  qemu.org | libguestfs.org



  reply	other threads:[~2026-09-25 21:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 18:37 [PATCH v3 0/4] iotests fixes Eric Farman
2026-08-13 18:37 ` [PATCH v3 1/4] iotests/nbd-in-qcow2-chain: use default machine Eric Farman
2026-09-24 13:04   ` Kevin Wolf
2026-09-25 21:01     ` Eric Blake [this message]
2026-08-13 18:37 ` [PATCH v3 2/4] iotests/nbd-tls-iothread: skip on non-x86 hardware Eric Farman
2026-08-13 18:37 ` [PATCH v3 3/4] iotests/fuse-truncate: skip if FUSE is not usable Eric Farman
2026-08-13 18:37 ` [PATCH v3 4/4] iotests/108: skip if fuse is unsuable Eric Farman
2026-09-24 13:00   ` Kevin Wolf
2026-09-24 14:55     ` Eric Farman
2026-09-23 15:51 ` [PATCH v3 0/4] iotests fixes Eric Farman

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=arbg_YqXp3hi49WK@redhat.com \
    --to=eblake@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@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.