This is a list of open work items and known bugs for the Xen on ARM with virtualization extension project.
In progress
Known Bugs
Versatile Express
linux v3.8-rc2 boot failed on versatile express
| Contact: xen-devel@lists.xen.org |
| Status: Fixed
|
| Description: Linux v3.8-rc2 fails to change the MMC voltage during boot on Versatile Express. |
| References: patch is needed to fix the bug. |
Arndale Board
Guest hang with multi-vcpu
| Contact: xen-devel@lists.xen.org |
| Status: Fixed
|
| Description: Hangs on the Arndale board with multi-vcpu guests. |
| References: patch is needed to fix the bug. |
Network doesn't work in the guest
| Contact: julien.grall@citrix.com |
| Status: In progress
|
| Description: Network doesn't work in the guest when an ehternet cable is plugged |
| References: http://pastebin.com/gEP3HdCg |
| Contact: xen-devel@lists.xen.org |
| Status: Open
|
| Description: When Xen tries to copy data from the guest, it fails to unmap some page because nobody(?) mapped it. |
| References: http://pastebin.com/frbeiuxz |
Open Work Items
vGIC interrupt prioritisation
| Contact: xen-devel@lists.xen.org |
| Description: Currently the vGIC only implements a very basic form of interrupt priority, in particular it is not able to preempt an inflight lower priority interrupt when a new higher priority one occurs. The emulation needs to consider the vCPUs current IAR as well as the priorities of pending and inflight interrupts. |
| References: Not specified, useful references. |
VCPU virtual time support
| Contact: xen-devel@lists.xen.org |
| Description: Currently the concept of virtual time exposed to the guests is very simplistic and is just a static offset from physical time based on the time when the guest was started. We need to consider if this is actually what is needed/wanted and consider cases such as stolen time etc. |
| References: Not specified, useful references. |
IOMMU support in Xen
| Contact: xen-devel@lists.xen.org |
| Description: write a driver in Xen for the ARM System Memory Management Unit (SMMU), use it to assign devices to Dom0. |
| References: Not specified, useful references. |
Autogenerate DomU's device trees
| Contact: xen-devel@lists.xen.org |
| Description: Xen or the Xen tools (ie. XL) should be able to generate the device tree for the guest automatically. |
| References: Not specified, useful references. |
Linux 64-bit on Xen
| Contact: Stefano Stabellini <stefano.stabellini@eu.citrix.com> |
| Description: Introduce Xen support for ARMv8 in Linux. |
| References: Not specified, useful references. |
Save/restore and migration
| Contact: xen-devel@lists.xen.org |
| Description: Make VM save/restore and VM migration work on ARM. |
| References: Not specified, useful references. |
Device assignment to DomUs
| Contact: xen-devel@lists.xen.org |
| Description: Assign one or more devices to an unprivileged guest, re-program the SMMU accordingly. |
| References: Not specified, useful references. |
Bootwrapper support for systems with non-HYP mode aware bootloaders and platform quirks
| Contact: xen-devel@lists.xen.org |
| Description: Currently Xen includes (in mode_switch.S, called from head.S) various workarounds for platforms which do not start the hypervisor in HYP mode and to initialise various board level values (either because when running on the model there is no firmware to do this or because the board firmware is buggy). In order to maintain the clean separation of such hacks from the main Xen code base and to achieve the single image goal this platform specific code should be extracted into a separate boot-wrapper project, similar to http://xenbits.xen.org/gitweb/?p=people/ianc/boot-wrapper.git;a=summary which can be used on the Fast Models. |
| References: Not specified, useful references. |
Expose Wallclock time to guests
| Contact: xen-devel@lists.xen.org |
| Description: Current Xen on ARM does not popular the wallclock time fields of the shared info with anything useful. It should do so... |
| References: Not specified, useful references. |
