* Separate out the test runner from the results collector/aggregator/controller so that you can run the test runner on a VM or vkernel, and collect the results on a different system. That way, if the system under test crashes, the tests can continue.
* Create necessary infrastructure, including provisioning, to be able to spin up VMs with DragonFly for testing, especially kernel testing. A first step would be to get this to work with spinning up vkernels.
+* Add support for per-testcase manifests instead of having to put everything in the runlist
* Integrate all tests we have into dfregress
* Add an html output generator like dfr2text. I have a started one laying around somewhere.
* Add more tests
* Difficulty: Medium-Hard
* Contact point: kernel@lists.dragonflybsd.org
+
+---
+
+#### Support KVM
+Add a KVM-compatible API to DragonFly, to be able to run qemu-kvm natively. This requires a fair bit of prior investigation as part of the proposal.
+
+[https://www.kernel.org/doc/Documentation/virtual/kvm/api.txt]
+
+Meta information:
+* Prerequisites: C, Kernel knowledge
+* Difficulty: Very Hard
+* Contact point: kernel@lists.dragonflybsd.org
+
+
---
+
##### Tickless Kernel
Make the DragonFly kernel tickless.
* Difficulty: Medium
* Contact point: Michael Neumann <mneumann@ntecs.de>, kernel@lists.dragonflybsd.org
+
---
##### Improve Kernel boot speed