Lines Matching full:guest

17 of the guest VM are secured so that a decrypted version is available only
18 within the VM itself. SEV guest VMs have the concept of private and shared
19 memory. Private memory is encrypted with the guest-specific key, while shared
36 When SEV is enabled, instruction pages and guest page tables are always treated
37 as private. All the DMA operations inside the guest must be performed on shared
38 memory. Since the memory encryption bit is controlled by the guest OS when it
53 			   system physical addresses, not guest physical
104 guest side implementation to function correctly. The below table lists the
105 expected guest behavior with various possible scenarios of guest/hypervisor
109 | Feature Enabled | Guest needs   | Guest has     | Guest boot       |
136 defines four privilege levels at which guest software can run. The most
142 levels, apart from the guest OS but still within the secure SNP environment.
143 They can provide services to the guest, like a vTPM, for example.
145 When a guest is not running at VMPL0, it needs to communicate with the software