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] Boot dom0 and mini-OS guest in parallel

To: Christopher Clark <christopher.w.clark@xxxxxxxxx>
Subject: Re: [Xen-devel] Boot dom0 and mini-OS guest in parallel
From: Rolf Neugebauer <rn@xxxxxxx>
Date: Thu, 9 Jul 2009 09:42:59 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Lucio Maciel <luciofm@xxxxxxxxx>, Rolf Neugebauer <rn@xxxxxxx>
Delivery-date: Thu, 09 Jul 2009 01:43:29 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=cPROmZ7wLbHs35WW9e+Za5mYJ2/aMxrURVSovEc6nMI=; b=p0IpOEYF0BPlnA7AOFvzFb/ij7HX9MpplFZuCHOKis810L8e8x6zvqMtfaEtbxH8sI akUk0E5FmH/zI+6C4j9aJ2Fdt3em3tN1Yhyh1gtxp+zoSyCzyXP9elCvnjwnyrAk16C4 Vo6RXWDmh+wiypf3X0l8xlBe1qvig7AbTfXWo=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=I3AY8vjXjbhGDN7Cq6Iju0kM+d4mKVOisxcFo0LYJoyEM+V6Lmk2rYo9UI3l6Ugr5K xIsiuXM+UawQS9iyJKqy0v278q5l2ADiqpQ00KtzJtLmsGb9OtsEwQISY997b1NUREyz Osa2DkkMBdU6/94Ww8ODYzy5sWT+k+y9kJG9A=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <eab087540907061447w54148c55v58487bd9ef07b2d3@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1d5458980907061340ncd0398cmdac17c408e5d4c84@xxxxxxxxxxxxxx> <eab087540907061447w54148c55v58487bd9ef07b2d3@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I've done something like this about 2 1/2 years ago. IIRC it was
pretty much what cristopher outlines below (dom0 build patches plus a
few other bits and bobs). I probably have the now heavily outdated
patches floating around somewhere. Drop me an email and I'll dig them


2009/7/6 Christopher Clark <christopher.w.clark@xxxxxxxxx>:
> It's not implemented now, as far as I can tell from a quick scan of
> the unstable source, but it's doable if you're up for a project.
> Xen does relocation of modules passed at boot which is how the dom0
> kernel and its initrd are loaded.
> You could specify another module to grub that Xen will relocate and
> then construct a domain around it within Xen, in a similar fashion to
> the way dom0 is constructed.
> See the dom0 construction code in:
> xen/arch/x86/domain_build.c : construct_dom0
> and
> xen/arch/x86/setup.c : __start_xen
> I'm not familar enough with ia64 to pass similar pointers there, and
> I'm not sure what it'd take to build a neat enough implementation that
> it'd be considered for merge.
> Christopher
> On Mon, Jul 6, 2009 at 1:40 PM, Lucio Maciel<luciofm@xxxxxxxxx> wrote:
>> Hi,
>> I'm using xen virtualization, and I writing a very security sensitive
>> software that I want to run completely isolated, running it on a
>> mini-OS or a very small/tight Linux guest.
>> That's OK, but I also want it to boot in parallel with dom0, directly
>> from the xen hypervisor, avoiding the need to first boot the dom0 and
>> then boot my small self-contained guest.
>> Is that possible? Or what should I know before trying to add this
>> functionality to the xen hypervisor?
>> Thanks in advance,
>> Lúcio Maciel
>> luciofm@xxxxxxxxx
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>