Automated builds and testing
- found broken 32-bit
- luiz suggested running against maintainer trees
- daniel gollub offered to take on maintenance
- integration with kvm-autotest?
- lucas, daniel, stefan...
- testing each git commit is probably overkill and too expensive
- current autotest run (each 48-hours to batch it up)
- stefan currently running once a day, autotest run is 3 hours, so
daily should work
- need an integration tree to run build test on?
- probably still too early
QEMU testing
- kvm unit tests
- small standalone kernel that exercises paths that have shown bugs
http://git.kernel.org/?p=virt/kvm/kvm-unit-tests.git;a=summary
- Michael Roth recent sent RFC for qtest
(http://www.mail-archive.com/qemu-devel@xxxxxxxxxx/msg54191.html)
- test module (->init(), ->run()) which runs in place of vcpu threads to
set up a test framework to do targetted testing, for example, of devices
- normal C code, access to qemu internal functions
- not just functional device testing, but can also to fuzz testing
- looking feedback/users/test developers/etc
- PPC (just kernel + initrd to boot, and verify boots are identical)
- full install in many cases is too long, and can trigger other issues
(alex had examples of emulation being slow enough that login screen
times out)
- tcg basic testing to verify qemu-kvm patch isn't breaking tcg
Cross version migration (new->old version migration thread)
- downstreams want this, support this upstream?
- versions vs. subsections (subsections should allow this to work)
- (as usual) more vmstate conversion needed
- qdev/vmstate both examples of partially completed work that need more
attention
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
