Hi,
> Ovmf can interpret the existence of an opt/ovmf/unaccepted_memory file
> I think "false" can mean either accept all memory or "do what you need
> to" and negotiate if the memory map boot service can create unaccepted
> memory entries. Whichever appears supported.
> Then "true" can be "do
I think the option should be boolean since it doesn't look like we're
going to need to tune the number very much.
It all boils down to "does the OS affirmatively support unaccepted
memory?" as in, we have no way to negotiate it, but force unaccepted
memory on.
Ovmf can interpret the existence of
On 6/16/2022 4:28 PM, Gerd Hoffmann wrote:
Hi,
After re-read and re-think, I think the problem is better to state as: we
need an interface for QEMU to tell OVMF how much memory it needs to accept,
from [Minimum to All]. So for the case that user wants to boot an
partial-enabled confidential
Hi,
> After re-read and re-think, I think the problem is better to state as: we
> need an interface for QEMU to tell OVMF how much memory it needs to accept,
> from [Minimum to All]. So for the case that user wants to boot an
> partial-enabled confidential VMs (like current Linux TDX and SNP
Cc: Xu, Min M ; Lendacky, Thomas
Subject: New "IndustryStandard" fw_cfg?
Hi y'all, I'm Dionna. I work on Confidential VMs at Google Cloud. I've been
keeping up with the TDX and SEV-SNP developments in OVMF and Linux,
and some in Qemu.
There's a new UEFI feature in v2.9 of the spe
On Thu, Jun 16, 2022 at 01:49:11PM +0800, Xiaoyao Li wrote:
> On 6/16/2022 1:37 PM, Gerd Hoffmann wrote:
> >Hi,
> >
> > > Per my understanding, Unaccepted Memory in UEFI is introduced for
> > > confidential VMs, i.e., for Intel TDX and AMD SEV-SNP. The only reason
> > > UEFI/OVMF reports
On 6/16/2022 1:37 PM, Gerd Hoffmann wrote:
Hi,
Per my understanding, Unaccepted Memory in UEFI is introduced for
confidential VMs, i.e., for Intel TDX and AMD SEV-SNP. The only reason
UEFI/OVMF reports "Unaccepted Memory" to OS, is a confidential VM is
desired.
No. Reporting "Unaccepted
Hi,
> Per my understanding, Unaccepted Memory in UEFI is introduced for
> confidential VMs, i.e., for Intel TDX and AMD SEV-SNP. The only reason
> UEFI/OVMF reports "Unaccepted Memory" to OS, is a confidential VM is
> desired.
No. Reporting "Unaccepted Memory" to the OS is not a hard
> > > For Qemu, the main code I see for adding config is here, but I'm not sure
> > > what y'all's preferred external configuration method is to get a value
> > > from an
>
> Ideally no external configuration, although I suspect we need something
> at least temporarily.
Yes, whereas TDX can
, 2022 2:09 AM
To: qemu-devel@nongnu.org
Cc: Xu, Min M ; Lendacky, Thomas
Subject: New "IndustryStandard" fw_cfg?
Hi y'all, I'm Dionna. I work on Confidential VMs at Google Cloud. I've
been
keeping up with the TDX and SEV-SNP developments in OVMF and Linux,
and some in Qemu.
There's
Cc: Xu, Min M ; Lendacky, Thomas
Subject: New "IndustryStandard" fw_cfg?
Hi y'all, I'm Dionna. I work on Confidential VMs at Google Cloud. I've been
keeping up with the TDX and SEV-SNP developments in OVMF and Linux,
and some in Qemu.
There's a new UEFI feature in v2.9 of the spe
Hi,
> > There's a new UEFI feature in v2.9 of the specification (March 2021) that
> > allows for memory ranges to be classified as "unaccepted", since both TDX
> > and SEV-SNP require that the guest VM accept any host-made changes to
> > page state. We should expect newer technologies on
Hi y'all, I'm Dionna. I work on Confidential VMs at Google Cloud. I've
been keeping up with the TDX and SEV-SNP developments in OVMF and
Linux, and some in Qemu.
There's a new UEFI feature in v2.9 of the specification (March 2021)
that allows for memory ranges to be classified as "unaccepted",
13 matches
Mail list logo
