From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Limpach Subject: Re: [PATCH] domain builder for ReactOS Date: Mon, 6 Jun 2005 19:33:54 +0100 Message-ID: <3d8eece20506061133627da9f7@mail.gmail.com> References: <200506022353.j52NrW8K032664@mailhost.geldorp.nl> <42A38B49.2020308@diku.dk> <3d8eece20506060149248d2e1@mail.gmail.com> <42A4158A.6070206@diku.dk> 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: <42A4158A.6070206@diku.dk> 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: Jacob Gorm Hansen Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 6/6/05, Jacob Gorm Hansen wrote: > Christian Limpach wrote: > > On 6/6/05, Jacob Gorm Hansen wrote: > > > >>Xen domUs need to have a bios, so we do not need to have domain-specifi= c > >>stuff like ELF-parsing in dom0. I will post to source to my 'mstrap' > >>attempt at this tomorrow for people to comment on. > > > > > > This is an option, but definitely not appropriate for every environment= . >=20 > Seems to work well for VMWare. Could you give an example of an > environment where this would not be appropriate? The model you suggest requires you to install the kernel such that it is accessible from within the guest environment. This is not always desirable nor practical. [some off-list exchange skipped] I like the loader + "ramdisk" solution. Can you reuse the code we have in the builder now to load elf, elf w/ symtab and bin images?=20 Isn't the development environment for the loader too hostile? I implemented a similar loader for NetBSD when the linux dom0 loader didn't support elf yet -- it was quite tedious to relocate stuff in memory so that the layout would be the same for the loader and the image it would execute... christian