qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Fabiano Rosas <farosas@suse.de>, qemu-devel@nongnu.org
Cc: "Juan Quintela" <quintela@redhat.com>,
	"Peter Xu" <peterx@redhat.com>,
	"Leonardo Bras" <leobras@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Laurent Vivier" <lvivier@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH v4 10/12] tests/qtest/migration: Support more than one QEMU binary
Date: Thu, 19 Oct 2023 08:46:56 +0200	[thread overview]
Message-ID: <e4645bfb-9ded-41cb-adc5-6c81effea275@redhat.com> (raw)
In-Reply-To: <20231018192741.25885-11-farosas@suse.de>

On 18/10/2023 21.27, Fabiano Rosas wrote:
> We have strict rules around migration compatibility between different
> QEMU versions but no test to validate the migration state between
> different binaries.
> 
> Add infrastructure to allow running the migration tests with two
> different QEMU binaries as migration source and destination.
> 
> The code now recognizes two new environment variables
> QTEST_QEMU_BINARY_SRC and QTEST_QEMU_BINARY_DST. In the absence of
> either of them, the test will use the QTEST_QEMU_BINARY variable. If
> both are missing then the tests are run with single binary as
> previously.
> 
> The machine type is selected automatically as the latest machine type
> version that works with both binaries.
> 
> Usage (only one of SRC|DST is allowed):
> 
> QTEST_QEMU_BINARY_SRC=../build-8.2.0/qemu-system-x86_64 \
> QTEST_QEMU_BINARY=../build-8.1.0/qemu-system-x86_64 \
> ./tests/qtest/migration-test
> 
> Reviewed-by: Juan Quintela <quintela@redhat.com>
> Signed-off-by: Fabiano Rosas <farosas@suse.de>
> ---
>   tests/qtest/migration-test.c | 28 ++++++++++++++++++++++++----
>   1 file changed, 24 insertions(+), 4 deletions(-)

Reviewed-by: Thomas Huth <thuth@redhat.com>

I wonder whether we could test this in the gitlab-CI, too, e.g. by using a 
Debian container and installing the qemu-system-x86_64 from the Debian 
distro there (since this should be close enough to an older version of an 
upstream release), then run the test with that version from Debian and the 
one that has just been compiled from the master branch? Anyway, just an 
idea, this can certainly be done later.

  Thomas



  reply	other threads:[~2023-10-19  6:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 19:27 [PATCH v4 00/12] tests/migration-test: Allow testing older machine types Fabiano Rosas
2023-10-18 19:27 ` [PATCH v4 01/12] tests/qtest: Allow qtest_qemu_binary to use a custom environment variable Fabiano Rosas
2023-10-18 19:27 ` [PATCH v4 02/12] tests/qtest: Introduce qtest_init_with_env Fabiano Rosas
2023-10-18 20:59   ` Peter Xu
2023-10-19 14:16     ` Fabiano Rosas
2023-10-18 19:27 ` [PATCH v4 03/12] tests/qtest: Allow qtest_get_machines to use an alternate QEMU binary Fabiano Rosas
2023-10-18 19:27 ` [PATCH v4 04/12] tests/qtest: Introduce qtest_has_machine_with_env Fabiano Rosas
2023-10-18 19:27 ` [PATCH v4 05/12] tests/qtest: Introduce qtest_resolve_machine_alias Fabiano Rosas
2023-10-18 19:27 ` [PATCH v4 06/12] tests/qtest/migration: Introduce find_common_machine_version Fabiano Rosas
2023-10-19  6:20   ` Thomas Huth
2023-10-18 19:27 ` [PATCH v4 07/12] tests/qtest/migration: Define a machine for all architectures Fabiano Rosas
2023-10-19  6:25   ` Thomas Huth
2023-10-19  8:07     ` Markus Armbruster
2023-10-19 11:57   ` Juan Quintela
2023-10-18 19:27 ` [PATCH v4 08/12] tests/qtest/migration: Specify the geometry of the bootsector Fabiano Rosas
2023-10-19  6:28   ` Thomas Huth
2023-10-19 11:59   ` Juan Quintela
2023-10-18 19:27 ` [PATCH v4 09/12] tests/qtest/migration: Set q35 as the default machine for x86_86 Fabiano Rosas
2023-10-19  6:28   ` Thomas Huth
2023-10-19 12:00   ` Juan Quintela
2023-10-18 19:27 ` [PATCH v4 10/12] tests/qtest/migration: Support more than one QEMU binary Fabiano Rosas
2023-10-19  6:46   ` Thomas Huth [this message]
2023-10-19 11:56     ` Juan Quintela
2023-10-19 14:06     ` Fabiano Rosas
2023-10-18 19:27 ` [PATCH v4 11/12] tests/qtest/migration: Allow user to specify a machine type Fabiano Rosas
2023-10-19  6:57   ` Thomas Huth
2023-10-19 12:06   ` Juan Quintela
2023-10-18 19:27 ` [PATCH v4 12/12] tests/qtest: Don't print messages from query instances Fabiano Rosas
2023-10-19 12:08 ` [PATCH v4 00/12] tests/migration-test: Allow testing older machine types Juan Quintela

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=e4645bfb-9ded-41cb-adc5-6c81effea275@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=farosas@suse.de \
    --cc=leobras@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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 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).