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


[Xen-devel] Re: Introduction to Linux based stubdom (GSoC 2011)

To: Steven Harp <steven.harp@xxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: Introduction to Linux based stubdom (GSoC 2011)
From: Jiageng Yu <yujiageng734@xxxxxxxxx>
Date: Wed, 11 May 2011 00:19:05 +0800
Cc: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Tue, 10 May 2011 09:20:00 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=qZke6ggv14R/0vG1QTKWp4I0lfmGn58cMCG4i7JIsL0=; b=hGc4aqfe+v5B17OaM4zRBTx1LJph7E9XF2QwU2JTBXlKkCMAr5o5p3bljQqLj//DRS nTgtCewQnx+Mwiko3kw+Q1pzqxIDJ400yLx9dGgDxcRHScSgn2iaMbWFh+WWNqjrpypQ CxK2q39AdIislfTy3zJYxCFsed+LGxiHt+jWc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=jtl2/F+tdNHr/p9gy0VWZ02ET1m0NMVRvawhQh6buBBsTIuHPEg2WBdilnODmUzHY6 Ps95kigiw19mt0T3zAOhEAv0XqZuEe6QMQbUnoaY8cIrPyvHGBz+eHIkeiLVug44hdhf z75E0MaNb6BWKSwM41GgPMntTIYnIurcLXv9g=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DC4271A.3090001@xxxxxxxxxxxxxxxxx>
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: <20110505163119363@xxxxxxxxxxxxxxxxxxxxxx> <4DC4271A.3090001@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Sat, May 7, 2011 at 12:51 AM, Steven Harp
<steven.harp@xxxxxxxxxxxxxxxxx> wrote:
> On 05/05/2011 11:31 AM, Jiageng Yu wrote:
>>     Stubdoms are very small Xen PV guests used to run some software
>> components that otherwise live in dom0. We plan to implement a linux
>> based stubdom, which provides devices emulation to a particular HVM
>> guest. The major tasks of this project are described below.
>>      1. We have to establish the environment of linux based stubdom
>> with minimal linux kernel and shared libraries, which could contain
>> the upstream qemu exactly. We also maintain a minimal upstream qemu by
>> cutting unnecessary objs in its configuration phase. The minimal linux
>> kernel, shared libraries and the upstream qemu are packed into the
>> ramdisk, which is the real body of stubdom we need.
> ...
>>     This is a brief introduction to the project. Any suggestion or
>> question will be Thankful!
> This is an excellent project.
> One suggestion regarding the minimal Linux is to make allowances
> in the build process for different kernel compilation options and
> supplemental files in the stubdom image.   Possibly worth thinking
> about different options for ramdisk, e.g. ramfs versus a compressed
> ext* filesystem. The former is lighter weight, but the latter
> offers more control, e.g. extended attributes.
> Best of luck,
>  Steve Harp

Hi Steven,

    Thanks very much for the advice. Honestly, until now, I have no
idea about the performance of Linux based stubdoms. So I try to make
it minimal first. Additionally, though a compressed ext* filesystem
could offer more control, stubdoms have little chance of accessing the
local filesystem in our current implementment plan.

    I will confirm with my mentor whether stubdoms need more
functional requirements. Thank you a lot.


Jiageng Yu.

Xen-devel mailing list

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