From: David Hildenbrand <david@redhat.com>
To: "Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org,
"Daniel P . Berrangé" <berrange@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] tests/functional/test_virtio_balloon: Only use KVM for running this test
Date: Fri, 7 Mar 2025 09:01:19 +0100 [thread overview]
Message-ID: <160b44eb-bf3f-45c9-b1ea-c82dbbe40bb0@redhat.com> (raw)
In-Reply-To: <20250307063904.1081961-1-thuth@redhat.com>
On 07.03.25 07:39, Thomas Huth wrote:
> The virtio_balloon test is currently hanging for unknown reasons
> when being run on the shared gitlab CI runners (which don't provide
> KVM, thus it's running in TCG mode there). All other functional tests
> that use the same asset (the Fedora 31 kernel) have already been
> marked to work only with KVM in the past, so those other tests are
> skipped on the shared gitlab CI runners. As long as the problem isn't
> fully understood and fixed, let's do the same with the virtio_balloon
> test to avoid that the CI is failing here.
Reviewed-by: David Hildenbrand <david@redhat.com>
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> tests/functional/test_virtio_balloon.py | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tests/functional/test_virtio_balloon.py b/tests/functional/test_virtio_balloon.py
> index 082bf08c4e8..5877b6c408c 100755
> --- a/tests/functional/test_virtio_balloon.py
> +++ b/tests/functional/test_virtio_balloon.py
> @@ -110,6 +110,7 @@ def assert_running_stats(self, then):
>
> def test_virtio_balloon_stats(self):
> self.set_machine('q35')
> + self.require_accelerator("kvm")
> kernel_path = self.ASSET_KERNEL.fetch()
> initrd_path = self.ASSET_INITRD.fetch()
> diskimage_path = self.ASSET_DISKIMAGE.fetch()
> @@ -122,7 +123,7 @@ def test_virtio_balloon_stats(self):
> # reset, we can reliably catch the clean stats again in BIOS
> # phase before the guest OS launches
> self.vm.add_args("-boot", "menu=on")
> - self.vm.add_args("-machine", "q35,accel=kvm:tcg")
> + self.vm.add_args("-accel", "kvm")
> self.vm.add_args("-device", "virtio-balloon,id=balloon")
> self.vm.add_args('-drive',
> f'file={diskimage_path},if=none,id=drv0,snapshot=on')
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2025-03-07 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 6:39 [PATCH] tests/functional/test_virtio_balloon: Only use KVM for running this test Thomas Huth
2025-03-07 8:01 ` David Hildenbrand [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=160b44eb-bf3f-45c9-b1ea-c82dbbe40bb0@redhat.com \
--to=david@redhat.com \
--cc=berrange@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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).