From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] applied: [PATCH] kvm: xsave set: mask-out PKRU bit in xfeatures if vCPU has no support
Date: Mon, 17 Jul 2023 11:03:36 +0200 [thread overview]
Message-ID: <0893eaee-e0e4-d0c2-4342-779795f071bf@proxmox.com> (raw)
In-Reply-To: <20230714183034.866091-1-t.lamprecht@proxmox.com>
Am 14.07.23 um 20:30 schrieb Thomas Lamprecht:
>
> If it gains us something we can drop this patch a bit in the future
> Proxmox VE 9 major release, but we should ensure that VMs that where
> started before PVE 8 cannot be directly live-migrated to the release
> that includes that change; so we should rather only drop it if the
> maintenance burden is high.
After live-migrating to a kernel with this patch, the flag won't show up
in subsequent migration blobs (i.e. guest_xsave->region) anymore, right?
So afterwards, you can migrate to kernels without this patch without
risking to trigger the issue. But there could still be snapshots from
before PVE 8 that can trigger the issue in PVE 9 if we'd drop this patch.
prev parent reply other threads:[~2023-07-17 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 18:30 Thomas Lamprecht
2023-07-17 9:03 ` Fiona Ebner [this message]
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=0893eaee-e0e4-d0c2-4342-779795f071bf@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/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