From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Anatol Belski <anbelski@linux.microsoft.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [RFC] virtio-villain: Guest fault injection for VMM robustness
Date: Mon, 6 Jul 2026 09:29:52 +0100 [thread overview]
Message-ID: <aktl-ojkXVZ4Jira@redhat.com> (raw)
In-Reply-To: <98dd26094403c204c7c2f0270d96b9c75842c7d8.camel@linux.microsoft.com>
On Sat, Jul 04, 2026 at 03:37:21PM +0200, Anatol Belski wrote:
> Hi,
>
> I would like to share virtio-villain, a guest side fault injection
> harness for virtio device models. The repository is at
> https://github.com/weltling/virtio-villain
>
> Comments on the approach, the coverage so far, and test cases worth
> adding are all welcome. While the tool targets multiple hypervisors,
> QEMU support is active and has already surfaced a few initial bugs.
snip
> Impact. Many findings have led to substantial improvements in
> virtio spec compliance and stability in Cloud Hypervisor, from
> input validation gaps to a config read that could take down a VM
> on aarch64. In QEMU the harness has surfaced a few guest triggered
> hangs and a double completion. The repository README lists the
> details with PR links and the test ID for each.
The README only lists cloud hypervisor bugs. Did you file any for
QEMU yet ?
If this is finding bugs in QEMU this test harness sounds like the kind
of thing we ought to have integrated in QEMU's meson test suite such
that it runs in CI to prevent regressions.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-07-06 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 13:37 [RFC] virtio-villain: Guest fault injection for VMM robustness Anatol Belski
2026-07-06 8:29 ` Daniel P. Berrangé [this message]
2026-07-06 19:22 ` Anatol Belski
2026-07-07 10:39 ` Daniel P. Berrangé
2026-07-07 21:09 ` Anatol Belski
2026-07-08 8:09 ` Daniel P. Berrangé
2026-07-08 18:25 ` Anatol Belski
2026-07-09 7:17 ` Daniel P. Berrangé
2026-07-09 10:02 ` Anatol Belski
2026-07-10 12:52 ` Matias Ezequiel Vara Larsen
2026-07-10 22:27 ` Anatol Belski
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=aktl-ojkXVZ4Jira@redhat.com \
--to=berrange@redhat.com \
--cc=anbelski@linux.microsoft.com \
--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.