From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [PATCH] raisin: disable stubdoms and etherboot in xen Date: Mon, 16 Nov 2015 09:39:28 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Thu, Nov 12, 2015 at 4:12 PM, Stefano Stabellini wrote: > Raisin is about cloning (or downloading) components explicitly and > independently, rather than having the Xen build system clone and build > stuff as part of the build process. > > Unfortunately it is not possible to build stubdoms outside the Xen tree > today, so just disable stubdoms for the moment. > > Similarly etherboot support requires downloading ipxe, so remove it for > now. So apart from stub domains, what does qemu-trad buy us over qemu-upstream now? Also, would it make sense to make it possible to build with a system ipxe? That's what CentOS does, FWIW. -George > > With this patch, building Xen via Raisin doesn't fetch anything from the > web, aside from what is configure in the config file. > > Signed-off-by: Stefano Stabellini > > --- > > diff --git a/components/xen b/components/xen > index 090cceb..894d119 100644 > --- a/components/xen > +++ b/components/xen > @@ -42,10 +42,13 @@ function xen_build() { > then > ovmf_opt="--enable-ovmf --with-system-ovmf="$BASEDIR"/ovmf-dir/ovmf.bin" > fi > + export ETHERBOOT_NICS="" > ./configure --prefix=$PREFIX --with-system-qemu=$PREFIX/lib/xen/bin/qemu-system-i386 \ > - --disable-qemu-traditional --enable-rombios $seabios_opt $ovmf_opt > + --disable-stubdom --disable-qemu-traditional \ > + --enable-rombios $seabios_opt $ovmf_opt > $RAISIN_MAKE > $RAISIN_MAKE install DESTDIR="$INST_DIR" > + unset ETHERBOOT_NICS > cd "$BASEDIR" > } > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel