From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?R8OpbWVzIEfDqXph?= Subject: Re: raisin and minios stubdom Date: Sat, 1 Apr 2017 20:00:29 +0200 Message-ID: <96ad4ee4-320f-b7aa-7694-295f491569aa@gmail.com> References: <20170327193819.GI19361@char.us.oracle.com> <16c8e69b-7076-8ab2-b6ea-29eab52ae278@gmail.com> <20170331140507.GD16644@char.us.oracle.com> <7c7794c7-2e5b-12d9-0d88-8350fffa0900@suse.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1568984276730078495==" Return-path: Received: from mail6.bemta6.messagelabs.com ([193.109.254.103]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cuNKD-0007nY-Em for xen-devel@lists.xenproject.org; Sat, 01 Apr 2017 18:00:33 +0000 Received: by mail-wm0-f46.google.com with SMTP id t189so20721610wmt.1 for ; Sat, 01 Apr 2017 11:00:31 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Juergen Gross Cc: xen-devel List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============1568984276730078495== Content-Type: multipart/alternative; boundary="------------DC0D6F31B9A2D2D2005876D9" This is a multi-part message in MIME format. --------------DC0D6F31B9A2D2D2005876D9 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 2017-04-01 08:19 keltezéssel, Géza Gémes írta: > > > 2017. márc. 31. 16:15 ezt írta ("Juergen Gross" >): > > On 31/03/17 16:05, Konrad Rzeszutek Wilk wrote: > > On Thu, Mar 30, 2017 at 07:42:48PM +0200, Gémes Géza wrote: > >> > >>> On Mon, Mar 27, 2017 at 09:28:14PM +0200, Gémes Géza wrote: > >>>> Hi, > >>>> > >>>> Currently the xen build system has optional support for > building a minios > >>>> (+needed libraries and tools) based stubdom. > >>>> > >>>> What is your opinion about moving support for building this > into raisin and > >>>> once that is stable drop support in the xen build system? > >>> Why? I do like doing 'make' and 'make install' and it doing > everything > >>> for me. > >>> > >>>> Cheers, > >>>> > >>>> Geza > >>>> > >>>> > >>>> _______________________________________________ > >>>> Xen-devel mailing list > >>>> Xen-devel@lists.xen.org > >>>> https://lists.xen.org/xen-devel > >> > >> Because it means that xen build needs to download and build a > lot of 3PP > >> components. Raisin is already designed to do so (it already > builds qemu-xen, > > > > If you do 'make src-tarball' it will do that for you - and you > can package > > all of that in a tarball. > > > >> qemu-traditional, libvirt and a few others). I think building > anything > >> besides xen proper would fit its scope better. > > > > OK, but that does not square well with RPM build systems. Those > are interested > > in building just one component (xen+toolstack+its extra pieces). > Using > > raisin to build everything is not going to fly. > > > > (Also distros like to seperate componets out - so they build > qemu-upstream > > seperate - which is used by Xen - and they could also do it for > MiniOS > > if they were spec files for it and such). > > There are only few stubdoms you can build without the Xen tree. How > would you do so for e.g. xenstore-stubdom needing the Xenstore sources > to be built? Several stubdoms need libxc built for stubdom included. > And you want to have a build error if e.g. a libxc modification is > breaking stubdom build. > > > Juergen > > Hi, > > Raisin already builds xen too, so it has all the dependencies ready. > Regarding the problem of breaking stubdom build by libxc changes I > think those can be prevented if we introduce osstests for raisin > build. Maybe we should start with that, adding raisin to the osstest > framework. > Opinions? > > Cheers > > Géza Regarding building distro rpms or debs with raisin that was never the scope of it. Raisin intends to be a quick method of building xen + a set of tools related to it, primarily for development purposes (https://wiki.xenproject.org/wiki/Raisin and https://blog.xenproject.org/2015/06/28/project-raisin-raise-xen/) Cheers, Géza --------------DC0D6F31B9A2D2D2005876D9 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
2017-04-01 08:19 keltezéssel, Géza Gémes írta:


2017. márc. 31. 16:15 ezt írta ("Juergen Gross" <jgross@suse.com>):
On 31/03/17 16:05, Konrad Rzeszutek Wilk wrote:
> On Thu, Mar 30, 2017 at 07:42:48PM +0200, Gémes Géza wrote:
>>
>>> On Mon, Mar 27, 2017 at 09:28:14PM +0200, Gémes Géza wrote:
>>>> Hi,
>>>>
>>>> Currently the xen build system has optional support for building a minios
>>>> (+needed libraries and tools) based stubdom.
>>>>
>>>> What is your opinion about moving support for building this into raisin and
>>>> once that is stable drop support in the xen build system?
>>> Why? I do like doing 'make' and 'make install' and it doing everything
>>> for me.
>>>
>>>> Cheers,
>>>>
>>>> Geza
>>>>
>>>>
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xen.org
>>>> https://lists.xen.org/xen-devel
>>
>> Because it means that xen build needs to download and build a lot of 3PP
>> components. Raisin is already designed to do so (it already builds qemu-xen,
>
> If you do 'make src-tarball' it will do that for you - and you can package
> all of that in a tarball.
>
>> qemu-traditional, libvirt and a few others). I think building anything
>> besides xen proper would fit its scope better.
>
> OK, but that does not square well with RPM build systems. Those are interested
> in building just one component (xen+toolstack+its extra pieces). Using
> raisin to build everything is not going to fly.
>
> (Also distros like to seperate componets out - so they build qemu-upstream
> seperate - which is used by Xen - and they could also do it for MiniOS
> if they were spec files for it and such).

There are only few stubdoms you can build without the Xen tree. How
would you do so for e.g. xenstore-stubdom needing the Xenstore sources
to be built? Several stubdoms need libxc built for stubdom included.
And you want to have a build error if e.g. a libxc modification is
breaking stubdom build.


Juergen
Hi,

Raisin already builds xen too, so it has all the dependencies ready. Regarding the problem of breaking stubdom build by libxc changes I think those can be prevented if we introduce osstests for raisin build. Maybe we should start with that, adding raisin to the osstest framework.
Opinions?

Cheers 

Géza 

Regarding building distro rpms or debs with raisin that was never the scope of it. Raisin intends to be a quick method of building xen + a set of tools related to it, primarily for development purposes (https://wiki.xenproject.org/wiki/Raisin and https://blog.xenproject.org/2015/06/28/project-raisin-raise-xen/)

Cheers,

Géza

--------------DC0D6F31B9A2D2D2005876D9-- --===============1568984276730078495== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============1568984276730078495==--