From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pve-devel-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 0B3F51FF15E for <inbox@lore.proxmox.com>; Tue, 11 Mar 2025 13:32:43 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 1B7DBF456; Tue, 11 Mar 2025 13:32:34 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1741696314; x=1742301114; d=canarybit.eu; s=rsa2; h=in-reply-to:content-type:mime-version:references:message-id:subject:cc:to: from:date:from; bh=AIo5nnj6GrPZu+c4kuwx5f6cRH0Sb/4L7a2kDseHvzE=; b=B4/Xlhk32lzaTJ0G+lgu4XcNGYdhB0ZNuHicBZtcBsC3yVGpzKBIG6W5XTTzPZry/xnFz147+Fos2 hNrbU6+wl96L3g/c/C46bhVUJzFmttnFFeVG9AxbKg1RpA0/DwC4lmvR4VIsON71Ll36+4Usxherdm O1Yh+WUtRVSQXBFZfaeMd+KdtMLzaRaYD2gkaDBbZZqvUo1fuobgWNbbXciV2NWz+Oy/ln3+Mvxdcd EfvwZN9GGkU2QgBHUDO8S8zp2rUex15XGVJ/w9LJ+SnQz/OzjhtpR+pXrPj9ufatARvP9o9HDqNmmC /9I4dOVC4/vaDAnsb7U3DJchC6a8u4w== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; t=1741696314; x=1742301114; d=canarybit.eu; s=ed2; h=in-reply-to:content-type:mime-version:references:message-id:subject:cc:to: from:date:from; bh=AIo5nnj6GrPZu+c4kuwx5f6cRH0Sb/4L7a2kDseHvzE=; b=QX30EmwJ7pLTM7q3F7W2bhMTsRS0epS0WMTDa599sqwz3cxARECgmO0diGJD2sFETDCqKMt3vDa2U 2DGpdyGCg== X-HalOne-ID: cff9da99-fe74-11ef-9cd1-d7c209f8bd06 Date: Tue, 11 Mar 2025 13:31:54 +0100 From: Philipp Giersfeld <philipp.giersfeld@canarybit.eu> To: Fiona Ebner <f.ebner@proxmox.com> Message-ID: <2oyay6zqur67bbgfk7vt425ibk7my37jsguzes7zgjokxxdx5k@yv2uzpisjimf> References: <20250224123714.2662460-1-philipp.giersfeld@canarybit.eu> <20250224123714.2662460-3-philipp.giersfeld@canarybit.eu> <f69d7f3c-d655-4173-b9e1-746b9e1f4fb3@proxmox.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <f69d7f3c-d655-4173-b9e1-746b9e1f4fb3@proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_MISSING 0.1 Missing DMARC policy KAM_SHORT 0.001 Use of a URL Shortener for very short URL RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Subject: Re: [pve-devel] [PATCH edk2-firmware v3 2/5] Add OVMF targets for AMD SEV-ES and SEV-SNP X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com> On 25/03/05 03:18PM, Fiona Ebner wrote: > Am 24.02.25 um 13:37 schrieb Philipp Giersfeld: > > AMD SEV-SNP boots with a single volatile firmware image OVMF.fd via the > > -bios option. > > > > Currently, an SEV-enabled VM will not boot with an OVMF > > firmware that was compiled with `SECURE_BOOT_ENABLE` [1]. > > > > Furthermore, during testing, SEV-enabled amchines did not boot with > > `SMM_REQUIRE`. > > > > Therefore, introduce a new target build-ovmf-cvm that builds OVMF > > firmware suitable for AMD SEV. > > > > [1] https://github.com/tianocore/edk2/pull/6285 > > > > This has been merged in edk2-stable202502, which is already out now. I'd > prefer going directly for that tag. Can we avoid splitting out the > SMM_REQUIRE flag then? > (Assuming you mean the SECURE_BOOT flag) Yes, I also prefer going directly for edk2-stable202502. I already tested it briefly and will prepare an updated version of the patch. Splitting out SMM cannot be avoided since SEV-ES and SEV-SNP do not support it [1,2]. [1] https://www.qemu.org/docs/master/system/i386/amd-memory-encryption.html [2] https://www.amd.com/content/dam/amd/en/documents/epyc-technical-docs/specifications/56421.pdf _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel