Virtio On Xen

From Xen


VirtIO on the Xen Hypervisor

There are three separate development approaches within the Xen community towards building support for enabling use of VirtIO device drivers in guest virtual machines with the Xen hypervisor, and a fourth older completed GSOC project. Work on the active approaches is proceeding on the xen-devel public mailing list.

Placeholder names have been assigned to each of these approaches for ease of reference in this page:

  • VirtIO-EPAM
  • VirtIO-SuSE
  • VirtIO-Argo
  • VirtIO-GSOC

In addition, Linaro has a project 'Stratos' pursuing: "Establish virtio as the standard interface between hypervisors, freeing a mobile, industrial or automotive platform to migrate between hypervisors and reuse the backend implementation."

The Stratos project teleconference calls are open.


VirtIO-EPAM: enabling existing VirtIO-MMIO transport on Xen, using foreign mappings and an IOREQ server

Development by EPAM and others, with focus on Xen on Arm platforms. Contact: Oleksandr Tyshchenko

Enables use of the existing standardized VirtIO-MMIO transport driver, which is present in the mainline Linux kernel, using Xen's IOREQ emulation infrastructure and use of privileged foreign mappings to establish shared memory for access to guest data by the device model backend.

Status: Patches are in progress towards Xen on the xen-devel mailing list. The presentation at Linaro Connect 2021 includes a working demonstration.

VirtIO on Xen hypervisor (Arm), Oleksandr Tyshchenko, EPAM, Linaro Connect 2021:


VirtIO-SuSE: introducing a new VirtIO transport driver that uses Xen grants

Developed by SuSE, presented at the Xen Design and Developer Summit 2021. Contact: Juergen Gross

A new VirtIO transport device driver is added to the guest kernel, to translate guest physical addresses into grant references, enabling VirtIO data path communication over mutually-negociated shared memory regions between the guest virtual machine and the device model backend. Improves isolation as backend does not need privilege over the guest to perform foreign mappings. Grant references are a Xen-specific interface. Design supports driver domains.

Status: A prototype is described in the presentation at the Xen Summit 2021.

VirtIO and Xen with Full Grant Support:


VirtIO-Argo: introducing a new VirtIO transport driver that uses Argo for interdomain communication, supporting isolation and Mandatory Access Control

Design and analysis performed within the OpenXT and Xen communities. Contact: Christopher Clark

A new VirtIO transport device driver is added to the guest kernel to transmit data between the guest domain and the domain hosting the device model via Argo rings: a Hypervisor-Mediated data eXchange protocol where the hypervisor transfers the data, being trusted to strictly adhere to the delivery protocol. Supports stronger isolation properties and enforcement of Mandatory Access Control security policy over interdomain communication. Does not use shared memory between domains. Development of a Hypervisor-agnostic interface for Argo has been proposed and discussed within the Xen community. Design supports driver domains.

Status: Design and analysis published; funding required for development to proceed.

VirtIO-Argo: Documentation at the OpenXT wiki:

VirtIO-Argo Development:

Minutes from the Argo HMX Transport for VirtIO topic call, 14th January 2021:

Xen-devel mailing list post, 30th September 2020 "VirtIO & Argo: a Linux VirtIO transport driver on Xen":


VirtIO-GSOC: 2011 Google Summer of Code Project

A Google Summer of Code project by Wei Liu investigated enabling VirtIO on Xen.

A working prototype was produced for both PV and HVM guests, using XenBus and the Qemu VirtIO backends. PV guests require a guest kernel patch to translate guest physical addresses to machine addresses in VirtIO rings.

Status: project completed.

Using the prototype

This section is intended to guide people who might be interested giving it a try.

Note:

Virtio for HVM guest

In fact, there is nothing much to do.

  • With this patch, we can enable libxl to support configuration for Virtio disk and nic.
    • For disk configuration syntax, use 'vd*' as virtual identifier, see docs/misc/vbd-interface.txt for details.
    • For nic configuration syntax, use 'model=virtio' in vif configuration. Latest QEMU may require 'model=virtio-net'. Just choose the one that works.
  • Disable MSI in guest kernel, with 'pci=nomsi' option in guest kernel command line. Currently, MSI delivery is not supported by HVM guest (though Xen has one HVMOP to do this, QEMU is not yet ready for this).
  • Also you might want to add 'xen_emul_unplug=never' in the guest kernel command line.

Use 'xl' to start the guest, not 'xm'.

Virtio for PV guest

First of all, you need the patch in the previous section to enable libxl to support configuration syntax for Virtio disk and nic.

Then apply the following patches to upstream QEMU and Linux kernel.

Run 'xl' to startup VM, 'xm' doesn't understand virtio configuration. After the VM is up, load modified virtio_ring.ko and all the other modules manually in the following order:

  1. virtio.ko
  2. virtio_ring.ko
  3. virtio_net.ko
  4. virtio_blk.ko
  5. virtio_xenbus.ko

Hopefully you will get Virtio devices without much trouble.

TODO

  • Enable xen-mapcache for Virtio for PV, improve performance.
  • Squash two evtchns into one, hopefully we can eliminate locking in transport layer and improve performance.
  • Enable Virtio device DMA capability
  • Bug fixes, transport layer crashes sometimes under heavy workload.

Related References

For those who encounter problems, please contact Wei Liu <liuw AT liuw SPAMFREE dot name>