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

From Xen
(V4V (historical))
(Hypervisor Mediated Exchange (HMX))
Line 6: Line 6:
* [https://www.platformsecuritysummit.com/2018/speaker/clark/ PSEC 2018 talk by Christopher Clark] (May 2018)
* [https://www.platformsecuritysummit.com/2018/speaker/clark/ PSEC 2018 talk by Christopher Clark] (May 2018)
* [https://www.youtube.com/watch?v=cnC0Tg3jqJQ Xen Summit 2019 talk by Christopher Clark] (June 2019)
* Xen Summit 2019 [https://www.youtube.com/watch?v=cnC0Tg3jqJQ video] and [https://static.sched.com/hosted_files/xensummit19/92/Argo%20and%20HMX%20-%20OpenXT%20-%20Christopher%20Clark%20-%20Xen%20Summit%202019.pdf slides] (June 2019)
== V4V (historical) ==
== V4V (historical) ==

Revision as of 13:50, 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 HP/Bromium uXen.


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.



Related Work