From: Christian Limpach <christian.limpach@gmail.com>
To: Jacob Gorm Hansen <jacobg@diku.dk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] domain builder for ReactOS
Date: Mon, 6 Jun 2005 19:33:54 +0100 [thread overview]
Message-ID: <3d8eece20506061133627da9f7@mail.gmail.com> (raw)
In-Reply-To: <42A4158A.6070206@diku.dk>
On 6/6/05, Jacob Gorm Hansen <jacobg@diku.dk> wrote:
> Christian Limpach wrote:
> > On 6/6/05, Jacob Gorm Hansen <jacobg@diku.dk> 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...
christian
next prev parent reply other threads:[~2005-06-06 18:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 21:51 [PATCH] domain builder for ReactOS Ge van Geldorp
2005-06-02 22:34 ` Christian Limpach
2005-06-02 22:51 ` Ge van Geldorp
2005-06-02 23:08 ` Christian Limpach
2005-06-02 23:53 ` Ge van Geldorp
2005-06-05 23:31 ` Jacob Gorm Hansen
2005-06-06 8:49 ` Christian Limpach
2005-06-06 9:21 ` Jacob Gorm Hansen
2005-06-06 18:33 ` Christian Limpach [this message]
2005-06-06 18:44 ` Jacob Gorm Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d8eece20506061133627da9f7@mail.gmail.com \
--to=christian.limpach@gmail.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=jacobg@diku.dk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.