Roadmap

[Ivan-Velickovic]

The main current priority for libvmm is to make the project more usable for real-world use. This means that a number of features are being worked on. Also, there is a high-priority in assessing the performance of the VMM and improving it.

The following table acts as a way of keeping the community updated with all the work being done on the project:

Feature	Implementation (Yes/In progress/No)	Pull Request/Branch	Merged status
RISC-V support	In progress	riscv branch	No
virtIO graphics	In progress	N/A	No
SMP guests	Yes	#116	No
GICv3 platform support	Yes	#47	Yes
SMC forwarding support	Yes	#119	Yes
ZCU102 support	Yes	#118	Yes
virtIO networking	Yes	#95	Yes
virtIO console	Yes	#26	Yes
virtIO block	Yes	#28	Yes
virtIO sound	Yes	#37	Yes

This not an exhaustive list, there is much more development planned but these are the things that are largely being worked on right now, or in the near future.

If you would like contribute to any of these or have particular features requests, let us know!

[Ivan-Velickovic]

Most of the items listed here are done or in progress (RISC-V support is in progress as is virtIO graphics).

The main things I'd like to see done before making libvmm considered not 'experimental' is a proper performance evaluation (we know there's something wrong there at least on ARM) and cleanup of various bits internally such as the vGIC driver.

From now on we'll probably just have individual issues for features rather than a roadmap issue like this.