Archived/Xen Development Projects: Difference between revisions
Rcpavlicek (talk | contribs) |
Lars.kurth (talk | contribs) (Removed GSoC and OPW 2014 projects) |
||
Line 69: | Line 69: | ||
* Xen PVSCSI supports both PV domUs and HVM guests with PV drivers. |
* Xen PVSCSI supports both PV domUs and HVM guests with PV drivers. |
||
* More info: http://wiki.xen.org/xenwiki/XenPVSCSI |
* More info: http://wiki.xen.org/xenwiki/XenPVSCSI |
||
{{Comment|[[User:Lars.kurth|Lars.kurth]] 14:14, 23 January 2013 (UTC):}} Should be suitable, but desc needs. Rate in terms of challenges, size and skill. Also kernel functionality is not yet upstreamed. Maybe Suse kernel. |
|||
}} |
|||
{{project |
|||
|Project=Implement Xen PVUSB support in xl/libxl toolstack |
|||
|Date=01/12/2012 |
|||
|Contact=Pasi Karkkainen <pasik@iki.fi> |
|||
|GSoC=Yes |
|||
|Desc= |
|||
xl/libxl does not currently support Xen PVUSB functionality. Port the feature from xm/xend to xl/libxl. Necessary operations include: |
|||
* Task 1: Implement PVUSB in xl/libxl, make it functionally equivalent to xm/xend. |
|||
* Send to xen-devel mailinglist for review, comments. |
|||
* Fix any upcoming issues. |
|||
* Repeat until merged to xen-unstable. |
|||
* See above for PVUSB drivers for dom0/domU. |
|||
* Xen PVUSB supports both PV domUs and HVM guests with PV drivers. |
|||
* More info: http://wiki.xen.org/xenwiki/XenUSBPassthrough |
|||
{{Comment|[[User:Lars.kurth|Lars.kurth]] 14:14, 23 January 2013 (UTC):}} Should be suitable, but desc needs. Rate in terms of challenges, size and skill. Also kernel functionality is not yet upstreamed. Maybe Suse kernel. |
{{Comment|[[User:Lars.kurth|Lars.kurth]] 14:14, 23 January 2013 (UTC):}} Should be suitable, but desc needs. Rate in terms of challenges, size and skill. Also kernel functionality is not yet upstreamed. Maybe Suse kernel. |
||
}} |
}} |
||
Line 124: | Line 107: | ||
}} |
}} |
||
{{project |
|||
|Project=Parallel xenwatch kthread |
|||
|Date=01/08/2012 |
|||
|Difficulty=Low-Medium |
|||
|Contact=Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> |
|||
|Desc= |
|||
Xenwatch is locked with a coarse lock. For a huge number of guests this represents a scalability issue. The need is to rewrite the xenwatch locking in order to support full scalability. |
|||
|Outcomes=Expected outcome: |
|||
* Have upstream patches. |
|||
* benchmark report of with and without. |
|||
|GSoC=Yes |
|||
}} |
|||
{{project |
{{project |
||
Line 198: | Line 167: | ||
For instance, implementing something like <code>alloc_page_on_any_node_but_the_current_one()</code> (or <code>any_node_except_this_guests_node_set()</code> for multinode guests), and have Xen's Tmem implementation use it (especially in combination with selfballooning), could solve a significant part of the NUMA problem when running Tmem-enabled guests. |
For instance, implementing something like <code>alloc_page_on_any_node_but_the_current_one()</code> (or <code>any_node_except_this_guests_node_set()</code> for multinode guests), and have Xen's Tmem implementation use it (especially in combination with selfballooning), could solve a significant part of the NUMA problem when running Tmem-enabled guests. |
||
}} |
}} |
||
{{project |
|||
|Project=HVM per-event-channel interrupts |
|||
|Date=01/30/2013 |
|||
|Contact=Paul Durrant <paul.durrant@citrix.com> |
|||
|Difficulty= |
|||
|Skills=C, some prior knowledge of Xen useful |
|||
|Desc=Windows PV drivers currently have to multiplex all event channel processing onto a single interrupt which is registered with Xen using the HVM_PARAM_CALLBACK_IRQ parameter. This results in a lack of scalability when multiple event channels are heavily used, such as when multiple VIFs in the VM as simultaneously under load. |
|||
Goal: Modify Xen to allow each event channel to be bound to a separate interrupt (the association being controlled by the PV drivers in the guest) to allow separate event channel interrupts to be handled by separate vCPUs. There should be no modifications required to the guest OS interrupt logic to support this (as there is with the current Linux PV-on-HVM code) as this will not be possible with a Windows guest. |
|||
|Outcomes=Code is submitted to xen-devel@xen.org for inclusion in xen-unstable |
|||
|GSoC=yes}} |
|||
=== Userspace Tools === |
=== Userspace Tools === |
||
Line 405: | Line 362: | ||
[[GSoC_2013#fuzz-testing-mirage]] |
[[GSoC_2013#fuzz-testing-mirage]] |
||
|Outcomes=1. a repo containing a fuzz testing tool; 2. some unexpected behaviour with a backtrace (NB it's not required that we find a critical bug, we just need to show the approach works) |
|Outcomes=1. a repo containing a fuzz testing tool; 2. some unexpected behaviour with a backtrace (NB it's not required that we find a critical bug, we just need to show the approach works) |
||
|GSoC=yes |
|||
}} |
|||
{{project |
|||
|Project=Mirage OS cloud API support |
|||
|Date=28/11/2012 |
|||
|Contact=Anil Madhavapeddy <anil@recoil.org> |
|||
|Skills=OCaml |
|||
|Difficulty=medium |
|||
|Desc= |
|||
MirageOS (http://openmirage.org) is a type-safe exokernel written in OCaml which generates highly specialised "appliance" VMs that run directly on Xen without requiring an intervening kernel. A MirageOS application typically runs via several communicating kernel instances on the cloud. Today these instances are difficult to manage; we would like to explore strategies for managing these distributed computations using common public cloud APIs such as those exposed by Amazon EC2 and Rackspace. |
|||
First we need to create pure OCaml API bindings for (e.g.) EC2 and Rackspace (purity is needed to ensure portability). These API bindings can then be used to provide operating-system-level abstractions to the exokernels. For example, a traditional VM might hotplug a vCPU; while a MirageOS application would request a "VM create" using the cloud API and "connect" the new instance to the existing network. We should be able to spin up 1000s of "CPUs" by using such APIs in a cluster environment. |
|||
As well as helping Xen/Mirage, the public cloud API bindings will be very useful to other people in other contexts-- a nice side-effect. |
|||
|Outcomes=1. one or more public cloud API bindings plus examples, in a standalone repo on github; 2. an example mirage app which uses these APIs to spin up a new VM |
|||
|GSoC=yes |
|GSoC=yes |
||
}} |
}} |
Revision as of 10:43, 22 April 2014
This page lists various Xen related development projects that can be picked up by anyone! If you're interesting in hacking Xen this is the place to start! Ready for the challenge?
To work on a project:
- Find a project that looks interesting (or a bug if you want to start with something simple)
- Send an email to xen-devel mailinglist and let us know you started working on a specific project.
- Post your ideas, questions, RFCs to xen-devel sooner than later so you can get comments and feedback.
- Send patches to xen-devel early for review so you can get feedback and be sure you're going into correct direction.
- Your work should be based on xen-unstable development tree, if it's Xen and/or tools related. After your patch has been merged to xen-unstable it can be backported to stable branches (Xen 4.2, Xen 4.1, etc).
- Your kernel related patches should be based on upstream kernel.org Linux git tree (latest version).
xen-devel mailinglist subscription and archives: http://lists.xensource.com/mailman/listinfo/xen-devel
Before to submit patches, please look at Submitting Xen Patches wiki page.
If you have new ideas, suggestions or development plans let us know and we'll update this list!
List of projects
Domain support
Upstreaming Xen PVSCSI drivers to mainline Linux kernel
|
Upstreaming Xen PVUSB drivers to mainline Linux kernel
|
Implement Xen PVSCSI support in xl/libxl toolstack
|
Block backend/frontend improvements
|
Utilize Intel QuickPath on network and block path.
|
Enabling the 9P File System transport as a paravirt device
|
OVMF Compatibility Support Module support in Xen
|
Hypervisor
Introducing PowerClamp-like driver for Xen
|
Integrating NUMA and Tmem
|
Userspace Tools
Refactor Linux hotplug scripts
|
XL to XCP VM motion
|
VM Snapshots
|
Allowing guests to boot with a passed-through GPU as the primary display
|
Advanced Scheduling Parameters
|
CPU/RAM/PCI diagram tool
|
KDD (Windows Debugger Stub) enhancements
|
Lazy restore using memory paging
|
CPUID Programming for Humans
|
Mirage and XAPI projects
There are separate wiki pages about XCP and XAPI related projects. Make sure you check these out aswell!
Create a tiny VM for easy load testing
|
Fuzz testing Xen with Mirage
|
From simulation to emulation to production: self-scaling apps
|
Towards a multi-language unikernel substrate for Xen
|
DRBD Integration
|
- XCP and XAPI development projects: XAPI project suggestions
- XCP short-term roadmap: XCP short term roadmap
- XCP monthly developer meetings: XCP Monthly Meetings
- XAPI developer guide: XAPI Developer Guide
Please see XenRepositories wiki page!