This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] domain builder for ReactOS

To: Jacob Gorm Hansen <jacobg@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH] domain builder for ReactOS
From: Christian Limpach <christian.limpach@xxxxxxxxx>
Date: Mon, 6 Jun 2005 19:33:54 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 06 Jun 2005 18:33:07 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ClpnbjPP/7e4E69g1yayXXy7+oURjDhD6kYbzbDCxs1q5s6k5BNDsUT1npMfQP71QpVuZFQFDVprB5v0iS+FJm2cXELCiMwbexBr/Rf4WClpxxXi082XPrQwH6ofrCpK//X7jyY6IN2mn++BSn99TU3rC0fr45NWPnjfsOfT2Ec=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <42A4158A.6070206@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <200506022353.j52NrW8K032664@xxxxxxxxxxxxxxxxxxx> <42A38B49.2020308@xxxxxxx> <3d8eece20506060149248d2e1@xxxxxxxxxxxxxx> <42A4158A.6070206@xxxxxxx>
Reply-to: Christian.Limpach@xxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 6/6/05, Jacob Gorm Hansen <jacobg@xxxxxxx> wrote:
> Christian Limpach wrote:
> > On 6/6/05, Jacob Gorm Hansen <jacobg@xxxxxxx> wrote:
> >
> >>Xen domUs need to have a bios, so we do not need to have domain-specific
> >>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.
> 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? 
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...


Xen-devel mailing list