Re: [Qemu-devel] Buildbot for qemu.git/master

[Lucas Meneghel Rodrigues <lmr@redhat.com>]

On Mon, 2011-02-07 at 15:15 +0000, Stefan Hajnoczi wrote:
> On Mon, Feb 7, 2011 at 3:02 PM, Richard W.M. Jones <rjones@redhat.com> wrote:
> >
> > On Sat, Feb 05, 2011 at 04:36:11PM +0000, Stefan Hajnoczi wrote:
> >> Occassionally a commit that breaks the build gets merged into
> >> qemu.git/master.  Build testing manually across all host platforms is
> >> not feasible for most developers.  Remember we cover 32- and 64-bit
> >> x86 Linux, Windows, and other host platforms.  There are factors like
> >> compile time but the main problem is that few have access to all host
> >> platforms.
> >
> > Is there a plan to test that the build minimally functions as well?
> > Could be as simple as running:
> >
> > ./x86_64-softmmu/qemu-system-x86_64 -L pc-bios \
> >  -kernel /boot/vmlinuz -nodefconfig -nographic -nodefaults -no-reboot \
> >  -m 500 -device virtio-serial -serial stdio -append 'panic=1 console=ttyS0'
> >
> > and just checking that it doesn't hang and does print out some
> > expected message near the end ("Kernel panic - not syncing: VFS:
> > Unable to mount root fs" might be a good one :-)
> 
> I'm not aware of a plan but if someone steps up with tests and
> machines that can serve as buildslaves, then the infrastructure can
> support it.
> 
> I believe KVM-Autotest does that and much more for KVM x86 but have
> never run it myself:
> http://www.linux-kvm.org/page/KVM-Autotest

Yes, it is, our current sanity jobs are much more comprehensive than
what was described. They currently:

* Install guests (RHEL6 and Win7 these days) on a number of option
scenarios (virtio, ide, large memory pages, etc)
* Boot them, making sure they are alive by performing remote login on
the guests
* Verify the hardware seen by the guest OS matches what we provided on
the command line
* Shut down the guests

Of course, we have other types of functional jobs, but just illustrating
what the framework can do today. It is possible to:

* Install a specific kernel build on the guest
* Choose what version of qemu user space to use for the testing

And we have some functionality to provision hosts using cobbler, that
will be sent upstream soon. It's a lot of automation infrastructure at
our service.