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

From Xen
(Argo)
(Argo)
Line 17: Line 17:
 
== Argo ==
 
== Argo ==
   
Argo was derived from V4V and patches were submitted to xen-devel in 2018 and merged in 2019 for Xen 4.12.
+
Argo was derived from V4V, hypervisor patches were submitted to xen-devel in 2018 and merged in 2019 for Xen 4.12.
  +
  +
Note: [https://github.com/OpenXT/linux-xen-argo Linux driver for Argo] is not yet upstream.
  +
  +
'''Upstream version'''
  +
  +
* [https://xenbits.xen.org/docs/unstable/designs/argo.html Xen 4.12 design doc] (March 2019)
  +
  +
'''History'''
   
 
* [[Media:DRAFT_RFC_Argo_and_HMX_2018-06-19-23-45.pdf| v0.1 design documentation for Argo]] (June 2018)
 
* [[Media:DRAFT_RFC_Argo_and_HMX_2018-06-19-23-45.pdf| v0.1 design documentation for Argo]] (June 2018)
Line 24: Line 32:
 
* [https://lists.xen.org/archives/html/xen-devel/2019-01/msg00310.html v3 patch series] (January 6 2019)
 
* [https://lists.xen.org/archives/html/xen-devel/2019-01/msg00310.html v3 patch series] (January 6 2019)
 
* [https://lists.xenproject.org/archives/html/xen-devel/2019-01/msg01051.html v4 patch series] (January 14, 2019)
 
* [https://lists.xenproject.org/archives/html/xen-devel/2019-01/msg01051.html v4 patch series] (January 14, 2019)
* [https://xenbits.xen.org/docs/unstable/designs/argo.html Xen 4.12 design doc] (March 2019)
 
   
 
== Related Work ==
 
== Related Work ==

Revision as of 13:41, 5 August 2020


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.

V4V (historical)

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

Argo

Argo was derived from V4V, hypervisor patches were submitted to xen-devel in 2018 and merged in 2019 for Xen 4.12.

Note: Linux driver for Argo is not yet upstream.

Upstream version

History

Related Work