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 2F7EA91913 for ; Mon, 14 Nov 2022 14:08:15 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0DCF22399F for ; Mon, 14 Nov 2022 14:07:45 +0100 (CET) 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, 14 Nov 2022 14:07:44 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 1BBC743CB4 for ; Mon, 14 Nov 2022 14:07:44 +0100 (CET) Message-ID: Date: Mon, 14 Nov 2022 14:07:43 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.0 Content-Language: en-US To: pve-devel@lists.proxmox.com, m.frank@proxmox.com References: <20221111142716.235955-1-m.frank@proxmox.com> <20221111142716.235955-3-m.frank@proxmox.com> From: Fiona Ebner In-Reply-To: <20221111142716.235955-3-m.frank@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: =?UTF-8?Q?0=0A=09?=AWL 0.028 Adjusted score from AWL reputation of From: =?UTF-8?Q?address=0A=09?=BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict =?UTF-8?Q?Alignment=0A=09?=NICE_REPLY_A -0.001 Looks like a legit reply (A) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF =?UTF-8?Q?Record=0A=09?=SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] [PATCH docs v2 2/2] added Memory Encryption documentation 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, 14 Nov 2022 13:08:15 -0000 Am 11.11.22 um 15:27 schrieb Markus Frank: > +* if there are problems while booting (stops at blank/splash screen or "Guest has not > +initialized the display (yet)") try to add virtio-rng and/or set "freeze: 1" > +so that you wait a few seconds before you click on *Resume* to boot. Doesn't sound very nice from a user perspective. Do you have an idea what's going on there? Can we automatically add some other kvm parameter to make it work (better) when SEV is configured? > + > +*Limitations:* > + > +* Because the memory is encrypted the memory usage on host is always wrong > +* Operations that involve saving or restoring memory like snapshots > +& live migration do not work yet or are attackable > +https://github.com/PSPReverse/amd-sev-migration-attack What happens if a user attempts a migration or snapshot right now? I think we should cleanly error out before even attempting if it can't work (yet).