diff options
| author | Michael Pratt <mpratt@google.com> | 2018-05-01 21:14:24 -0700 |
|---|---|---|
| committer | Shentubot <shentubot@google.com> | 2018-05-01 21:15:08 -0700 |
| commit | 185233427b3834086a9050336113f9e22176fa3b (patch) | |
| tree | 826a80cc815b6c15bb1717719adde4b7f3d3b070 | |
| parent | 43256efb080915d92a17549d86ef4eaff9ab8ef8 (diff) | |
Note that the KVM platform is experimental
PiperOrigin-RevId: 195043285
Change-Id: Ie76112eff61062e1a54894b3707201fd284be377
| -rw-r--r-- | README.md | 13 |
1 files changed, 7 insertions, 6 deletions
@@ -142,12 +142,13 @@ mapping functionality. Today, gVisor supports two platforms: executing host system calls. This platform can run anywhere that `ptrace` works (even VMs without nested virtualization). -* The **KVM** platform allows the Sentry to act as both guest OS and VMM, - switching back and forth between the two worlds seamlessly. The KVM platform - can run on bare-metal or on a VM with nested virtualization enabled. While - there is no virtualized hardware layer -- the sandbox retains a process model - -- gVisor leverages virtualization extensions available on modern processors - in order to improve isolation and performance of address space switches. +* The **KVM** platform (experimental) allows the Sentry to act as both guest OS + and VMM, switching back and forth between the two worlds seamlessly. The KVM + platform can run on bare-metal or on a VM with nested virtualization enabled. + While there is no virtualized hardware layer -- the sandbox retains a process + model -- gVisor leverages virtualization extensions available on modern + processors in order to improve isolation and performance of address space + switches. ### Performance |