From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Limpach Subject: Re: [PATCH] domain builder for ReactOS Date: Thu, 2 Jun 2005 23:34:53 +0100 Message-ID: <3d8eece20506021534605d3af5@mail.gmail.com> References: <200506022151.j52LpxH0032269@mailhost.geldorp.nl> Reply-To: Christian.Limpach@cl.cam.ac.uk Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <200506022151.j52LpxH0032269@mailhost.geldorp.nl> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ge van Geldorp Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 6/2/05, Ge van Geldorp wrote: > As announced earlier (http://lists.xensource.com/archives/html/xen-devel/= 2005-03/msg01160.html) > I'm working on porting ReactOS to Xen. The first stage, getting our bootl= oader > running, is complete now. Progress report and a screenshot on > http://reactos.com/wiki/index.php/Xen_port >=20 > To start ReactOS in a Xen domain, a ReactOS domain builder is needed. Pat= ches > to implement that are included below. I'm not too keen on this approach: we try to keep the number of domain builders small. Ideally we'd only want one builder for paravirtualized guests and one for hardware assisted guests. For paravirtualized guests, this is the mis-named "linux builder". We have a plan9 specific builder because plan9 uses a.out, but I think it would be preferable to support additional file format loaders within the linux builder. Why do you think that you need a different builder? Especially since you're going to use a bootloader anyway, your actual kernel image file can be of whatever format you like... If your main/only struggle is with the ELF format, then please consider adding support for additional loaders in the existing builder. christian