Lines Matching refs:hypervisor

8 face of a hypervisor/VMM that has been compromised and may behave maliciously.
72 and must be trusted by the guest OS. By implication, the hypervisor/VMM must
132   happens in the paravisor in the guest context (instead of the hypervisor/VMM
141   hypervisor/VMM. This is done via callbacks invoked from
145   that the paravisor can coordinate the transitions and inform the hypervisor
148 * Interrupt injection. In fully enlightened mode, a malicious hypervisor
161 directly to the hypervisor, just as in a non-CoCo VM. But in paravisor mode,
163 hypervisor. But the paravisor is idiosyncratic in this regard, and a few
165 hypervisor. These hypercall sites test for a paravisor being present, and use
238 the untrusted host partition and the untrusted hypervisor. Instead, the guest
245 and the paravisor, ensuring that sensitive data is protected from hypervisor-
263 nor the hypervisor has any access to the data. The guest needs to establish
362 guest actually wants to communicate with the hypervisor, it has to use special
365 guest chose to communicate directly to the hypervisor, they use the hypervisor
367 (non-confidential, using the VMBus relay) and use the hypervisor SynIC, and
392 hypervisor of the transition mark pages as "not present" while a transition