Re: [Qemu-devel] The state of testing

[mdroth]

On Mon, Mar 04, 2013 at 05:22:34PM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> > How are things looking with device emulation, migration, monitor, char, etc?
> 
> At the moment autotest/virt-test is pretty much the only workable thing
> for non-trivial devices because libqtest lacks infrastructure for pci
> and anything building on top of pci.
> 
> usb has no in-tree tests, but has autotest coverage.
> 
> chardevs have some autotest coverage, /me wrote a test for
> chardev-{add,remove} qmp commands.  Still need to rebase + polish +
> submit that one though.
> 
> Migration coverage is pretty bad overall I think.

I've been working on a tool to try to do build-bot-like coverage for
cross-version migration. It's basically a fork of Anthony's qemu-test
suite that uses the same qemu-jeos/initrd system and a single test
harness with pre-migration/post-migration/post-migration reboots tests
case.

The plan is to get it in-tree along with qemu-test, with a wrapper
that'll test current->current migration as part of `make check`, and set up
a test bot with older qemu builds to test cross-version compatibility and
generate a report along these lines:

http://wiki.qemu.org/Migration/Compatibility

I can throw the code up somewhere if anyone is interested, but it's
mostly for internal testing atm.

> What is the state of the idl patch series btw?

The IDL to generate serialization routines for device state is fairly
well-fleshed out, but there was a lot of flux in the code-parser to
process them in later stages of getting the initial code upstreamed, so
I wanted to hold off a bit to refactor the parser and consider some
alternatives (namely, Peter's suggestion of generating device structs
from a higher-level IDL, or leveraging other tools to generate the ASTs)

I should have some cycles to work on it more after the 1.4.1 release.

> 
> cheers,
>   Gerd
>