From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pj1-f44.google.com (mail-pj1-f44.google.com [209.85.216.44]) by mx.groups.io with SMTP id smtpd.web10.582.1666127794102850661 for ; Tue, 18 Oct 2022 14:16:34 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=oPcJYjzS; spf=pass (domain: gmail.com, ip: 209.85.216.44, mailfrom: pedro.falcato@gmail.com) Received: by mail-pj1-f44.google.com with SMTP id 70so15202412pjo.4; Tue, 18 Oct 2022 14:16:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7qPlSHQFWFeec/WbnPPERihmhkfxFKMgyLkV+lnQs54=; b=oPcJYjzSb+vBY58MT6Hti0rNGuDTsQhOP6AIVHFI8p04+QAJxCmQ5e5bNifUCpGVo8 7u7peiZog6/IFlJ0NWTO8NVJMI+J03xldL6W0b1UwgHnFO8sItlEbsE6E0eBNqfxeriy m9xaMfPuBJwge/gHPcgBOZhgSqGccGjDI0rBHQ7nMLUNt+0eOlEyffntd/su0hjMEKrY YC6l1GjxMW2wbP/p3J7hgEL5H72G2ZduXp/ICWsEkhKAIyKOOcWF2k7lTpGYE9JIKQxl tz16unVuAQyTpTOsk5vh7LpJuouKGNbbFCWTF3OkvofF4No5ZjAAFE9AThZvBPGJaW67 PNww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7qPlSHQFWFeec/WbnPPERihmhkfxFKMgyLkV+lnQs54=; b=oe8GEiSSnHT2OpLLCoeJgp5PL0/AU8CQIf7R8Y/5Zs0ms6hO127EnkMMl7RYmXoE/G 7iZb4NgeF1v/j+SJ3Wbxj1bE2DHwK/7KrQDwlb/o7VdvKCIqj6SsLUqFlNM9ZYr+/x3d 8ul1z7knY+o8/BArEwTXwO5XIyzP/tDPcScz2KuOdteyK5Tu8/jn5YymVtzeeDsDGJCJ eEpp7OShoDzDKVywqcgKq/sFI9DorVEWzgPIJ/U8Js985ubI4gogax49kqeEa3lTPGHK SrWgomxY3hUqqu/m+kh6Xt5ijd6eu3gZicS8AcoKEyj1dYvmoGdoP8o3GeJXUu6AIg2T 8g1A== X-Gm-Message-State: ACrzQf0uKEwNdXCfpTlIwxsF+0oQTbVzGBFlyQly1xdfCHMLPylNJk2W 8p58MKaPAQs6NkFMjk9621Rgrue3b5v2ihu8wW7RdnNUPTY= X-Google-Smtp-Source: AMsMyM7uabHTHiKfdDWMYK6mwGaK8ESoPMoStsjmxlTR7qgdu+9PWDzsO+uSoi2bzQhrvu0337lce/mEJG8ldtMhsQo= X-Received: by 2002:a17:90b:4d08:b0:20a:6861:352c with SMTP id mw8-20020a17090b4d0800b0020a6861352cmr5696708pjb.225.1666127793251; Tue, 18 Oct 2022 14:16:33 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "Pedro Falcato" Date: Tue, 18 Oct 2022 22:16:21 +0100 Message-ID: Subject: Re: [edk2-rfc] Boot Order not persistent : UEFI variables not getting stored in NVRAM disk ? To: rfc@edk2.groups.io, het.gala@nutanix.com Cc: edk2-devel-groups-io Content-Type: multipart/alternative; boundary="000000000000446b5d05eb559bd3" --000000000000446b5d05eb559bd3 Content-Type: text/plain; charset="UTF-8" Hi, (cc devel) NVRAM has nothing to do with disks or EFI partitions. Are you using OVMF? How are you using it? OVMF itself emulates variable storage if you run it in the wrong way. On Tue, Oct 18, 2022 at 4:00 PM wrote: > Hi EDK2 community, > > I have a used case, where I am trying to change boot order for multiboot > (multiple OS) systems and for singleboot systems. I was able to change the > boot order and set auto boot time-out only if there is EFI partition > available in a disk. The boot order is not persisted i.e. on a VM reboot, > the boot order sets back to default in absence of disk or EFI partition in > disk. Even though there is a NVRAM disk available, I am not able to change > the boot order in UEFI firmware settings. So, I have a couple of doubts > regarding this, so decided to start with a discussion. > 1. Is it necessary to have EFI partition in disks to store UEFI variables > like boot order / auto boot time-out and others ? > 2. Does the workflow of OVMF demands to store the UEFI variables only into > EFI partition and not into NVRAM disk ? > > > > > > -- Pedro Falcato --000000000000446b5d05eb559bd3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

(cc devel)
NVR= AM has nothing to do with disks or EFI partitions.
Are you us= ing OVMF? How are you using it? OVMF itself emulates variable storage if yo= u run it in the wrong way.

On Tue, Oct 18, 2022 at 4:00 PM <het.gala@nutanix.com> wrote:
Hi EDK2 community,=

I have a used case, where I am trying to change boot order for multiboot (m= ultiple OS) systems and for singleboot systems. I was able to change the bo= ot order and set auto boot time-out only if there is EFI partition availabl= e in a disk. The boot order is not persisted i.e. on a VM reboot, the boot = order sets back to default in absence of disk or EFI partition in disk. Eve= n though there is a NVRAM disk available, I am not able to change the boot = order in UEFI firmware settings. So, I have a couple of doubts regarding th= is, so decided to start with a discussion.
1. Is it necessary to have EFI partition in disks to store UEFI variables l= ike boot order / auto boot time-out and others ?
2. Does the workflow of OVMF demands to store the UEFI variables only into = EFI partition and not into NVRAM disk ?







--
Pedro Falcato
--000000000000446b5d05eb559bd3--