Sunday, July 26, 2009

Upcoming Xen 4.0 May Provide Full Support for AMD's IOMMU

Click here for Xen Roadmap


Xen Product Roadmap

Xen 3.4 is now live. The following features/enhancements are proposed for Xen 4.0; see the complete community list at Wiki Roadmap:

  • RDMA Live Migration Support
  • Dom0 kernel in Linux 2.6.30 or later
  • Dom0 support for Marvell 6480 disk driver
  • Pass through USB-Controllers/Devices for PV Guests
  • Fault Tolerance - Project Remus and/or Kemari
  • Monitor, Limit, Control network traffic coming at DomUs
  • Internationalization / Unicode Support
  • Configure Virtual Bridge like Real Switch (e.g. Control VLAN, port status)
  • VLan tagging per NIC int he VM Config File
  • Virtual Ethernet Switch
  • Physical Xen boot/install support via native UEFI (pUEFI) and virtual UEFI (vUEFI) support
  • Limit I/O for individual disks of VM (similar to credit scheduler weight)
  • Dynamic Memory Management for Overcommiting RAM
  • PCI CGA Passthrough for VT-d (vendor cards like Nvidia, AIT, etc)
  • Full AMD IOMMU Support
  • Online resizing of DomU Disks
  • Cross compliling Xen and Modular Builds
If you are interested in new features, please submit your ideas for Xen 4.0 to the xen-devel mailing list.


Click here for Xen 4.0 Feature Requests List


Here is the active Xen 4.0 Feature Requests

  • Robert Dunkley ( - RDMA Live Migration Support (allow for faster and smoohter live migration when

using Infiniband or Iwarp NICS)

  • Luke Crawford ( - Dom0 kernel in Linux 2.6.30 kernel and Marvell 6480 disk driver

  • Franz Von Hahn [] - stable support for passing through usb-controllers/devices and pci-devices for paravirtualized guests would be really great.

  • Fault Tolerance - Project Remus and/or Kemari
  • Kashif Ali ( - Monitor, Limit, & Control network traffic coming at DomUs

  • Nathan Stratton [] - RDMA infiniband support for migration

  • Ramachandran Radhakrishnan [] - Internationalization / Unicode support

  • Alessandro R. [] - A tool that permit to configure virtual bridge like real switch (e.g.

control VLAN, port status etc.); VLan tagging per NIC in the VM config file; Xen with a Virtual Ethernet Switch (like VDE2)? You can create a switch per client ; from Kieran Mansley [] : With Xen (and other virtualisation technologies) users often end up with a set of bridges, v-switches, hardware switches, and now switches (albeit limited in capabilities) in virtualisation-aware NICs. It would be very useful to develop a control plane over all these devices to allow them to be sensibly configured from a single point. I know there are some people working on bits of this problem but bringing it all together to work on Xen, using open APIs and protocols so that other technologies could be easily integrated, would help a lot.

  • Dong Wei ( - the physical Xen boot/install support via native UEFI (pUEFI) and virtual UEFI (vUEFI) support

  • Thiago Camargo Martins Cordeiro []- Virtual Ethernet Switch, virtual uplinks (through SSH, for example), virtual cables, virtual plugs, so I can create a virtual switch per client on each of my dom0 of my cluster, or maybe it needs a easy way to integrate itself with VDE2.

  • Philipp Schmid ( - Limit I/O for individual disks of VM (similar to credit scheduler weight)

  • Francesco Gallo ( - Dynamic Memoery Management for Overcommitting RAM

  • Sander Eikelenboom [] - as many others .. VGA (pci-e/pci) passthrough, complete USB passthrough, (also working for webcams/videograbbers etc) ; i'm currently working with "USB over IP" from the project. It is working fine for printers/scanners, and almost perfect for webcam (some little distortion left). But functionality within XEN would be better.

  • Paul Schulze [] - Fully functional USB passthrough would be really nice to have, but to be useful, I would also like to also request some sort of device management, that allows automatically assigning devices to a DomU whenever it is connected and a way to have unknown devices assigned to a default DomU. Otherwise, interaction on the Dom0 will be needed for each and every time, a device is connected; Comments form Sander Eikelenboom [] Good point, some good and flexible management would be nice to have too. USBIP at the moment can handle:

- remove binding to currently loaded modules - binding to usbip at plugin time In some quite simple userspace management tools. For xen it think xend would be the place for normal rules, and xm for hotplug ? It would be nice if you could make the rules for usb passthrough match with both usb port numbers as well as device id's, perhaps even with wildcards.