From: "Jürgen Groß" <jgross@suse.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Linux PV/PVH domU crash on (guest) resume from suspend
Date: Wed, 17 Feb 2021 07:51:42 +0100 [thread overview]
Message-ID: <0b71a671-592a-53ab-6b4a-1fe15b9eb453@suse.com> (raw)
In-Reply-To: <YCylpKU8F+Hsg8YL@mail-itl>
[-- Attachment #1.1.1: Type: text/plain, Size: 893 bytes --]
On 17.02.21 06:12, Marek Marczykowski-Górecki wrote:
> Hi,
>
> I'm observing Linux PV/PVH guest crash when I resume it from sleep. I do
> this with:
>
> virsh -c xen dompmsuspend <vmname> mem
> virsh -c xen dompmwakeup <vmname>
>
> But it's possible to trigger it with plain xl too:
>
> xl save -c <vmname> <some-file>
>
> The same on HVM works fine.
>
> This is on Xen 4.14.1, and with guest kernel 5.4.90, the same happens
> with 5.4.98. Dom0 kernel is the same, but I'm not sure if that's
> relevant here. I can reliably reproduce it.
This is already on my list of issues to look at.
The problem seems to be related to the XSA-332 patches. You could try
the patches I've sent out recently addressing other fallout from XSA-332
which _might_ fix this issue, too:
https://patchew.org/Xen/20210211101616.13788-1-jgross@suse.com/
Juergen
[-- Attachment #1.1.2: OpenPGP_0xB0DE9DD628BF132F.asc --]
[-- Type: application/pgp-keys, Size: 3135 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2021-02-17 6:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 5:12 Linux PV/PVH domU crash on (guest) resume from suspend Marek Marczykowski-Górecki
2021-02-17 6:51 ` Jürgen Groß [this message]
2021-02-17 13:48 ` Marek Marczykowski-Górecki
2021-02-17 15:37 ` Jürgen Groß
2021-02-19 12:48 ` Jürgen Groß
2021-02-19 13:10 ` Jan Beulich
2021-02-19 13:18 ` Jürgen Groß
2021-02-19 13:37 ` Jan Beulich
2021-02-19 13:41 ` Jürgen Groß
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=0b71a671-592a-53ab-6b4a-1fe15b9eb453@suse.com \
--to=jgross@suse.com \
--cc=marmarek@invisiblethingslab.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).