Re: [Qemu-devel] xen build failure

[Stefano Stabellini]

On Wed, 18 Apr 2012, Stefan Hajnoczi wrote:
> On Wed, Apr 18, 2012 at 09:26:44AM +0200, Alexander Graf wrote:
> > 
> > On 17.04.2012, at 18:53, Stefano Stabellini wrote:
> > 
> > > On Tue, 17 Apr 2012, Alon Levy wrote:
> > >> I have xen-devel-4.1.2-14.fc17.x86_64 and am getting the following build
> > >> error:
> > >> 
> > >>  CC    x86_64-softmmu/xen-all.o
> > >> /home/alon/src/spice_upstream/qemu/xen-all.c: In function 
> > >> ‘xen_hvm_inject_msi’:
> > >> /home/alon/src/spice_upstream/qemu/xen-all.c:132:5: error: implicit 
> > >> declaration of function ‘xc_hvm_inject_msi’ 
> > >> [-Werror=implicit-function-declaration]
> > >> /home/alon/src/spice_upstream/qemu/xen-all.c:132:5: error: nested extern 
> > >> declaration of ‘xc_hvm_inject_msi’ [-Werror=nested-externs]
> > >> 
> > >> commit f1dbf015dfb0aa7f66f710a1f1bc58b662951de2 seems to be missing a
> > >> capability / version check.
> > > 
> > > Thanks for the report!
> > > I tested it without Xen and with Xen 4.2 but not with Xen 4.1 :-/
> > 
> > So that means that our buildbot coverage is missing Xen 4.1 :). Could you 
> > guys possibly provide a machine with Xen 4.1 that'd be running buildbot so 
> > we see at least the compile time issues? :)
> 
> It would be good to have buildslave for Xen versions.  Here is more info
> on how to volunteer a buildslave:
> 
> http://wiki.qemu.org/ContinuousIntegration

I think it is a very good idea, I'll try to set one up.
Can I pass an arbitrary set of options to configure?
Otherwise I'll setup one VM per Xen version we want to test, I guess at
least three: 4.0, 4.1 and 4.2.