From: Liam Merwick <liam.merwick@oracle.com>
To: "Jörg Rödel" <joro@8bytes.org>
Cc: coconut-svsm@lists.linux.dev, linux-coco@lists.linux.dev
Subject: Re: SVSM: Updated Linux and QEMU branches available for testing
Date: Wed, 2 Sep 2026 14:54:46 +0100 [thread overview]
Message-ID: <8bfed259-d508-46ba-8604-283359f01d52@oracle.com> (raw)
In-Reply-To: <apfpXc1bKIG9dCwX@8bytes.org>
On 02/09/2026 10:18, Jörg Rödel wrote:
> Hi Liam, On Wed, Sep 02, 2026 at 12: 00: 54AM +0100, Liam Merwick wrote:
> > Another data point. The machine I encountered this issue is a Genoa >
> machine. I did a fresh install on a Turin and another Genoa and those >
> do not reproduce
>
> Hi Liam,
>
> On Wed, Sep 02, 2026 at 12:00:54AM +0100, Liam Merwick wrote:
>> Another data point. The machine I encountered this issue is a Genoa
>> machine. I did a fresh install on a Turin and another Genoa and those
>> do not reproduce the issue - the latest SVSM branches work on those.
>
> I pushed a fix to the svsm-v7.2 branch of
>
> https://github.com/coconut-svsm/qemu
>
> Did you test with this latest version of QEMU on the failing Genoa machine? For
> reference, the HEAD points at commit 5c1c05b2c3aa0dd1248e0cf58e401626e30887f8.
>
Yes, thanks. With this QEMU fix everything works correctly.
Regards,
Liam
next prev parent reply other threads:[~2026-09-02 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 16:17 SVSM: Updated Linux and QEMU branches available for testing Jörg Rödel
2026-08-31 8:41 ` Liam Merwick
2026-08-31 15:24 ` Jörg Rödel
2026-09-01 0:58 ` Liam Merwick
2026-09-01 6:48 ` Jörg Rödel
2026-09-01 7:07 ` Jörg Rödel
2026-09-01 23:00 ` Liam Merwick
2026-09-02 9:18 ` Jörg Rödel
2026-09-02 13:54 ` Liam Merwick [this message]
2026-09-09 17:12 ` Stefano Garzarella
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=8bfed259-d508-46ba-8604-283359f01d52@oracle.com \
--to=liam.merwick@oracle.com \
--cc=coconut-svsm@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-coco@lists.linux.dev \
/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.