From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, m.frank@proxmox.com
Subject: Re: [pve-devel] [PATCH docs v2 2/2] added Memory Encryption documentation
Date: Mon, 14 Nov 2022 14:07:43 +0100 [thread overview]
Message-ID: <e9e252fd-f049-6cb2-1ace-4583600e94c5@proxmox.com> (raw)
In-Reply-To: <20221111142716.235955-3-m.frank@proxmox.com>
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).
prev parent reply other threads:[~2022-11-14 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 14:27 [pve-devel] [PATCH qemu-server/docs v2 0/2] AMD SEV Markus Frank
2022-11-11 14:27 ` [pve-devel] [PATCH qemu-server v2 1/2] QEMU AMD SEV enable Markus Frank
2022-11-14 13:06 ` Fiona Ebner
2022-11-17 10:50 ` Markus Frank
2022-11-17 11:27 ` Fiona Ebner
2022-11-11 14:27 ` [pve-devel] [PATCH docs v2 2/2] added Memory Encryption documentation Markus Frank
2022-11-11 14:48 ` Matthias Heiserer
2022-11-14 13:07 ` Fiona Ebner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e9e252fd-f049-6cb2-1ace-4583600e94c5@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=m.frank@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.