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

Re: [Xen-devel] [PATCH v9 5/6] Clone and build Seabios by default



On Tue, 2011-12-13 at 18:22 +0000, Stefano Stabellini wrote:
> On Tue, 13 Dec 2011, Ian Jackson wrote:
> > Stefano Stabellini writes ("Re: [Xen-devel] [PATCH v9 5/6] Clone and build 
> > Seabios by default"):
> > > On Tue, 13 Dec 2011, Ian Jackson wrote:
> > > > Stefano Stabellini writes ("Re: [Xen-devel] [PATCH v9 5/6] Clone and 
> > > > build Seabios by default"):
> > > > > On Mon, 12 Dec 2011, Ian Campbell wrote:
> > > > > > On Mon, 2011-12-12 at 17:39 +0000, Ian Jackson wrote:
> > > > > > > I see you have included a lockstep changeset number in 
> > > > > > > xen-unstable
> > > > > > > but are we really able to force these to update in lockstep ?
> > > > 
> > > > Did you have an answer for this ?
> > > 
> > > The answer is yes. Unless there is a bug that I didn't manage to find of
> > > course.
> > 
> > That doesn't sound like an answer to my question.
> > 
> > To put it another way: are we intending to permanently maintain a
> > branch of seabios and a branch of qemu upstream ?  Are we going to
> > have one such branch for each branch of Xen ?  Are we expecting our
> > downstreams to use our specific version of qemu and seabios, rather
> > than building from upstream ?
> 
> I think "yes" in case of qemu, at the very least for the different
> release times of the xen and qemu projects.

Unfortunately I expect that distros will want to package qemu once (from
upstream) with support for all the various options, including Xen,
enabled and depend on that in their Xen packaging rather than packaging
a slightly different qemu a second time.

I'm not sure how we can address this without exploding our test matrix.
It seems like we need to test at a minimum the current qemu stable and
development branches :-/

> I don't have an opinion on seabios because I am nore sure how many
> changes are we going to make to it. However I recall that you and/or
> IanC were in favor of having or own branch of seabios as well.

I think that even if we never diverge from upstream and irrespective of
whether we stick in lockstep or not we should host a tree to point our
users (and default build) at. This gives us flexibility if we ever do
need to diverge and also isolates our users from issues with 3rd party
servers.

> BTW I think it is probably better if IanC maintains seabios if we decide
> to have our own branch, given that he is the one that did most of the
> work on it so far.

I'm happy to do that.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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