From: Anthony Liguori <aliguori@us.ibm.com>
To: Gerd Hoffmann <kraxel@suse.de>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>,
Xen devel list <xen-devel@lists.xensource.com>
Subject: Re: [RFC/patch] domain builder rewrite
Date: Tue, 13 Jun 2006 08:54:33 -0500 [thread overview]
Message-ID: <448EC399.2070404@us.ibm.com> (raw)
In-Reply-To: <448EB8B5.5010205@suse.de>
Gerd Hoffmann wrote:
>> I guess that the hypervisor really doesn't need to know about ELF
>> images at all? To me it seems that it should be enough for it to get a
>> suspended image built by the domain.
>>
>
> It needs to know to bootstrap domain 0 only, all other domains are
> created by the tools, not the hypervisor itself.
>
It always struck me as odd that we duplicated the domain builder code in
both in userspace and in the hypervisor. Have you given any thought of
unifying the two?
I always thought it would be neat to have a hypercall that could build
paravirt domains at least...
Regards,
Anthony Liguori
> cheers,
>
> Gerd
>
>
next prev parent reply other threads:[~2006-06-13 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 14:59 [RFC/patch] domain builder rewrite Gerd Hoffmann
2006-06-13 12:51 ` Simon Kagstrom
2006-06-13 13:08 ` Gerd Hoffmann
2006-06-13 13:54 ` Anthony Liguori [this message]
2006-06-13 15:15 ` Gerd Hoffmann
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=448EC399.2070404@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=kraxel@suse.de \
--cc=simon.kagstrom@bth.se \
--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.