From: Markus Frank <m.frank@proxmox.com>
To: Dietmar Maurer <dietmar@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-docs] added Memory Encryption documentation
Date: Fri, 10 Jun 2022 10:51:45 +0200 [thread overview]
Message-ID: <5655a15f-e0e3-1ec0-937e-45cee832d405@proxmox.com> (raw)
In-Reply-To: <2131917860.4411.1654835841666@webmail.proxmox.com>
Not really. All i could find are these patches:
https://marc.info/?l=kvm&m=156278967226011&w=2
https://lore.kernel.org/all/20190809185434.GH2840@work-vm/T/#m902085a219bdad35007dd7fffa0ed0765fd2322a
In the documentation of qemu snapshots&live migration is still a TODO:
https://www.qemu.org/docs/master/system/i386/amd-memory-encryption.html
Current Limitations Section in the suse documentation:
https://documentation.suse.com/sles/15-SP3/html/SLES-amd-sev/article-amd-sev.html
Also interesting "Migration Attack" when using these patches:
https://github.com/PSPReverse/amd-sev-migration-attack
On 6/10/22 06:37, Dietmar Maurer wrote:
> Live migration works?
>
>> +Limitations:
>> +
>> +* Memory usage on host is always wrong and around 82% Usage
>> +* Snapshots do not work
>> +* edk2-OVMF required
>> +* Recommendable: VirtIO RNG for more entropy (VMs sometimes will not
next prev parent reply other threads:[~2022-06-10 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 4:37 Dietmar Maurer
2022-06-10 8:51 ` Markus Frank [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-09 11:14 [pve-devel] [PATCH qemu-server] QEMU AMD SEV enable Markus Frank
2022-06-09 11:14 ` [pve-devel] [PATCH pve-docs] added Memory Encryption documentation Markus Frank
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=5655a15f-e0e3-1ec0-937e-45cee832d405@proxmox.com \
--to=m.frank@proxmox.com \
--cc=dietmar@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal