From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 2CB47D9C3 for ; Mon, 17 Jul 2023 11:03:42 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 15B1AB312 for ; Mon, 17 Jul 2023 11:03:42 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Mon, 17 Jul 2023 11:03:41 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 60098426EC for ; Mon, 17 Jul 2023 11:03:41 +0200 (CEST) Message-ID: <0893eaee-e0e4-d0c2-4342-779795f071bf@proxmox.com> Date: Mon, 17 Jul 2023 11:03:36 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Content-Language: en-US To: Proxmox VE development discussion , Thomas Lamprecht References: <20230714183034.866091-1-t.lamprecht@proxmox.com> From: Fiona Ebner In-Reply-To: <20230714183034.866091-1-t.lamprecht@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.001 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.091 Looks like a legit reply (A) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [pve-devel] applied: [PATCH] kvm: xsave set: mask-out PKRU bit in xfeatures if vCPU has no support X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jul 2023 09:03:42 -0000 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.