Difference between revisions of "Argo: Hypervisor-Mediated Exchange (HMX) for Xen"

From Xen
(Argo)
Line 21: Line 21:
 
* [https://docs.google.com/document/d/1VUPdWwd1raDOPhjReVVkmb6YoQB3X5oU12E4ExjO1n0/view Minutes of x86 community call] (September 2018)
 
* [https://docs.google.com/document/d/1VUPdWwd1raDOPhjReVVkmb6YoQB3X5oU12E4ExjO1n0/view Minutes of x86 community call] (September 2018)
 
* [https://lists.xen.org/archives/html/xen-devel/2018-12/msg00005.html v1 patch series] (November 2018)
 
* [https://lists.xen.org/archives/html/xen-devel/2018-12/msg00005.html v1 patch series] (November 2018)
 +
* [https://lists.xen.org/archives/html/xen-devel/2019-01/msg00310.html v3 patch series] (January 2019)
  
 
== Related Work ==
 
== Related Work ==

Revision as of 19:10, 9 January 2019


Hypervisor Mediated Exchange (HMX)

The technologies provided by VMMs for communication between VMs have a critical impact on VM isolation properties, on the confidence components can have in the delivery of data and in the integrity of the data that is received. The video below identifies aspects of inter-VM communication system architecture that support important properties that are valuable for building secure systems. Terminology is introduced to enable classification of the existing body of art and survey relevant communication technologies in modern hypervisor, OS and microkernel systems. An example is presented — Argo, an inter-VM communication mechanism developed for the Xen hypervisor — and how it is distinguished from other communication channels on the Xen platform and elsewhere.

PSEC 2018 talk by Christopher Clark (May 2018)

V4V (historical)

V4V was created for Citrix XenClient and derivatives are currently deployed in production systems for OpenXT and Bromium uXen.

Argo

Argo is derived from V4V and patches will be submitted to xen-devel in 2018.

Related Work