[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Update seabios and upstream qemu versions used on xen-unstable

2014-04-15 19:59 GMT+02:00 Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>:
On Tue, Apr 15, 2014 at 04:33:22PM +0200, Fabio Fantoni wrote:
> Il 15/04/2014 15:24, George Dunlap ha scritto:
> >On 04/15/2014 12:51 PM, Sander Eikelenboom wrote:
> >>
> >>Tuesday, April 15, 2014, 1:18:32 PM, you wrote:
> >>
> >>>On Mon, Apr 14, 2014 at 01:11:36PM +0200, Fabio Fantoni wrote:
> >>>>I think it would be good to update seabios and upstream qemu
> >>>>versions used
> >>>>with xen-unstable.
> >>>>Recently I tested on my testing system with xen-unstable
> >>>>seabios updated to
> >>>>debian package version 1.7.4-4 without finding regressions
> >>>>and upstream qemu
> >>>>2.0-rc0 from git where I found 2 regressions already
> >>>>reported and solved on
> >>>>upstream git.
> >>>>I updated qemu to 2.0-rc2 where I did some tests without finding other
> >>>>regressions or bugs for now.
> >>>>I also noticed on the wiki page of the next hackathon the
> >>>>topic "QEMU and
> >>>>SeaBIOS regression testing". As I reported some time ago it
> >>>>would be of
> >>>>great help.
> >>
> >>>I was thinking of submitting the update for QEMU when QEMU 2.0 will be
> >>>out.
> >>
> >>Wouldn't it be sensible for xen-unstable to follow at least the
> >>qemu rc's so those
> >>get build and tested in the osstests ?
> >
> >It might make more sense to have a osstest target that used
> >vanilla upstream -- in fact, there may be one already.
> >
> > -George
> Yes is the vanilla upstream test that is missing, at least testing
> each stable version from rc0 can be a start but test daily or weekly
> git master would be perfect.
> Now only upstream qemu of xen git is tested but is old of some
> upstream versions ago and the merging with newer versions for now
> were always after a long time out of the stable upstream version :(


Is that something you would be comfortable taking a look at? I fear
that a lot of us are busy with some of the hypervisor development and
this is kind of on the end of the plate - which means we would probably
get to it but not right away :-(

From qemu 1.3 I kept testing the upstream qemu as far as I could, to find and report any regressions with xen.
Unfortunately I did not have enough time and in some cases the knowledge to fix and/or improve some things to try to ensure a good integration, use of the main new qemu features, and exemptions from criticism regressions with xen before of the new qemu stable versions release.
An important first step, perhaps the most important would be to keep the tested with qemu upstream xen during the development of each version (http://git.qemu.org/?p=qemu.git;a=shortlog;h=refs/heads/master) in order to immediately identify any regression with xen and resolve as soon as possible or at least report it on qemu-devel.
I gave a quick look at the git osstest to eventually try to use it on a test server and run necessary automated tests for the nights but I did not understand enough and I have almost no knowledge of perl, and perhaps even more my very bad english...

My first doubts about osstest for example:
must to have 2 test systems (osstest controller and test xen host) on a network that is without others dhcp and dns servers outside of the controller but connected to the internet or am I wrong?

There is a method to easy and fast have working dns/dhcp/tftp enough to osstest?

Thanks for any reply and sorry for my bad english.
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.