From: Jan Beulich <jbeulich@suse.com>
To: George Dunlap <gwd@xenproject.org>
Cc: Juergen Gross <jgross@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Linux PV domU with >1 vCPU never resumes after xl save/restore
Date: Tue, 4 Aug 2026 10:02:42 +0200 [thread overview]
Message-ID: <61b9c9fb-3d97-4480-8171-bce986e698a8@suse.com> (raw)
In-Reply-To: <CAFLBxZZLYxk4ZZZ9++B9qRn_J8X6ochbHr4037mbC8sDfsRqDA@mail.gmail.com>
On 04.08.2026 08:12, George Dunlap wrote:
> Saving and restoring a multi-vcpu PV guest appears to have been broken in
> Linux for some time (observed 6.6.56 and 6.12.86). Report below from
> Claude Fable; I've independently verified the behavior on vanilla Linux
> 6.6.56. Claude seems to think it's a bug in Linux.
Just to double check, as there was a crucial fix there recently: This is with
a Xen including bedbc17d8407 ("x86/domctl: restore all registers in
arch_{get,set}_info_guest()")?
Jan
next prev parent reply other threads:[~2026-08-04 8:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 6:12 Linux PV domU with >1 vCPU never resumes after xl save/restore George Dunlap
2026-08-04 8:02 ` Jan Beulich [this message]
2026-08-04 8:45 ` Jürgen Groß
[not found] ` <CAFLBxZYffb3bOS4Zz8m2QX52J6V9-ZonaxPCULoqyRLpPKh-VQ@mail.gmail.com>
[not found] ` <e9cffe43-f3d2-4af1-a429-7c83e98daec5@suse.com>
2026-08-05 12:15 ` Dual content (text/plain and text/html) on xen-devel (was Re: Linux PV domU with >1 vCPU never resumes after xl save/restore) George Dunlap
2026-08-05 12:41 ` Jürgen Groß
2026-08-05 13:21 ` George Dunlap
2026-08-05 13:28 ` Jan Beulich
2026-08-05 14:03 ` Jürgen Groß
2026-08-10 8:52 ` George Dunlap
2026-08-05 14:03 ` George Dunlap
2026-08-04 10:07 ` Linux PV domU with >1 vCPU never resumes after xl save/restore George Dunlap
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=61b9c9fb-3d97-4480-8171-bce986e698a8@suse.com \
--to=jbeulich@suse.com \
--cc=gwd@xenproject.org \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xenproject.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.