All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anatol Belski <anbelski@linux.microsoft.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [RFC] virtio-villain: Guest fault injection for VMM robustness
Date: Thu, 09 Jul 2026 12:02:13 +0200	[thread overview]
Message-ID: <17b658d35228733829d128c09de142b5c195ffc3.camel@linux.microsoft.com> (raw)
In-Reply-To: <ak9LAQDQMIZjWor5@redhat.com>

On Thu, 2026-07-09 at 08:17 +0100, Daniel P. Berrangé wrote:


> We don't have any stock kernel. Tests refer to any kenrel/initrd
> image that they require and download it via the "Asset" class
> functions which have caching built-in.

Thanks. With this I have all the info to try, I think. The CH kernel
will do fine then, I will just point the asset reference at that
release.

Meanwhile, I have filed the first finding on the tracker
https://gitlab.com/qemu-project/qemu/-/work_items/3968

Will follow up with the rest on a slower pace, as discussed.

Regards

Anatol


  reply	other threads:[~2026-07-09 10:03 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é
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 [this message]
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=17b658d35228733829d128c09de142b5c195ffc3.camel@linux.microsoft.com \
    --to=anbelski@linux.microsoft.com \
    --cc=berrange@redhat.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.