On Thu, Sep 22, 2016 at 04:12:04PM -0500, Brijesh Singh wrote:
> Hi,
>
> On 09/22/2016 10:12 AM, Paolo Bonzini wrote:
> >
> >
> > >
> > > to use encrypted guest launch
> > > # $QEMU \
> > > -object sev-receive-info,id=launch0 \
> > > -object sev-send-info,id=send0 \
> > >
Hi,
On 09/22/2016 10:12 AM, Paolo Bonzini wrote:
to use encrypted guest launch
# $QEMU \
-object sev-receive-info,id=launch0 \
-object sev-send-info,id=send0 \
-object sev-guest-info,id=sev0,launch=launch0,send=send0 \
.
References to other objects should be
On Thu, Sep 22, 2016 at 10:52:49AM -0400, Brijesh Singh wrote:
> # $QEMU \
> -object sev-receive-info,id=launch0,flags.ks=off \
> -object sev-guest-info,id=sev0,launch=launch0 \
> -object security-policy,id=secure0,memory-encryption=sev0 \
> -machine ,security-policy=secure0
On 22/09/2016 16:52, Brijesh Singh wrote:
> to launch unencrypted SEV guest:
> # $QEMU \
> -object sev-launch-info,id=launch0,flags.ks=off \
> -object sev-guest-info,id,sev0,launch=launch0 \
> -object security-policy,id=secure0,memory-encryption=sev0 \
> -machine
This patch adds the initial support required to integrate Secure
Encrypted Virtualization (SEV) feature. SEV is an extension to the
existing AMD-V technology found on AMD processors. The SEV feature
allows the memory contents of a virtual machine to be transparently
encrypted with a key unique to
