From: "Jörg Rödel" <joro@8bytes.org>
To: Liam Merwick <liam.merwick@oracle.com>
Cc: coconut-svsm@lists.linux.dev, linux-coco@lists.linux.dev
Subject: Re: SVSM: Updated Linux and QEMU branches available for testing
Date: Mon, 31 Aug 2026 17:24:53 +0200 [thread overview]
Message-ID: <apWcYdRjTeZF5vtH@8bytes.org> (raw)
In-Reply-To: <b1cfe9d8-4f29-42f0-b3ac-312724250d0c@oracle.com>
Hi Liam,
On Mon, Aug 31, 2026 at 09:41:13AM +0100, Liam Merwick wrote:
>
> On 27/08/2026 17:17, Jörg Rödel wrote:
> > Hi, I just pushed out new branches for COCONUT-SVSMs downstream Linux
> > and QEMU changes. The new branches need to be used together, as there
> > have been rebases which changed parts of the user-space interface. For
> > Linux the branch is:
> > https: //github. com/coconut-svsm/linux/tree/svsm-v7. 2
> >
>
>
> On a system that was running the 7.1 branches, I've upgraded the host
> kernel and qemu to the 7.2 branches and am now getting CPU stalls in
> the guest (and eventual boot hang).
>
> I'm using ./scripts/launch_guest.sh (and 2026.08-devel)
>
> One thing I've noticed with kvm_stat is that the top host functions are
>
> Event Total %Total CurAvg/s
> kvm_set_irq 2304824 22.2 2095
> kvm_ioapic_set_irq 2304824 22.2 2095
> kvm_pic_set_irq 2304768 22.2 2095
> kvm_exit 626814 6.0 159
> kvm_entry 626814 6.0 159
> kvm_vmgexit_exit 299778 2.9 105
> kvm_vmgexit_enter 299777 2.9 105
> (...)
Thanks for testing the new branches. Can you please share your exact
launch_guest.sh command line? Also, what type of guest image are you running,
something I can download as well?
-Joerg
next prev parent reply other threads:[~2026-08-31 15:25 UTC|newest]
Thread overview: 9+ 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 [this message]
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
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=apWcYdRjTeZF5vtH@8bytes.org \
--to=joro@8bytes.org \
--cc=coconut-svsm@lists.linux.dev \
--cc=liam.merwick@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox