From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Fajar A. Nugraha" <list@fajar.net>
Subject: Re: FW: HXEN on linux
Date: Wed, 7 Sep 2011 20:56:12 +0700
Message-ID: <CAG1y0sdQRMH64PHwz-UarFh6=UviphE1qGNjR+OLQpLSq2argg@mail.gmail.com>
References: <90F0F47595235141A4380FCF01B0185B20BC426222@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>
	<20110809195159.GA7834@dumpdata.com>
	<90F0F47595235141A4380FCF01B0185B20BC513BCB@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>
	<alpine.DEB.2.00.1108251522360.12963@kaball-desktop>
	<90F0F47595235141A4380FCF01B0185B20BC585A8A@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>
	<alpine.DEB.2.00.1108261305220.12963@kaball-desktop>
	<90F0F47595235141A4380FCF01B0185B20BC608BBC@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>
	<20110901134638.GB23971@dumpdata.com>
	<90F0F47595235141A4380FCF01B0185B2240FEA5E3@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>
	<20110906161258.GA5264@dumpdata.com>
	<90F0F47595235141A4380FCF01B0185B2240FEADDE@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <90F0F47595235141A4380FCF01B0185B2240FEADDE@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "Deepak Kr. Sharma - ERS, HCL Tech" <deepak.s@hcl.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On Wed, Sep 7, 2011 at 7:19 PM, Deepak  Kr. Sharma - ERS, HCL Tech
<deepak.s@hcl.com> wrote:
> Hello Konrad,
>
> We are part of COE team and our priorities are driven by team that does t=
echnology tracking (mix of sales and delivery). As recommended by them, Xen=
 is type-1 hypervisor and HXen is a type-2 hypervisor. Virtualization in a =
product is a value-add service and not the core product functionality. No o=
ne would want to touch a stable system (which is a must in case of type-1 h=
ypervisor) for a value-add service. Hence, HXen gives flexibility to add fe=
atures on VM w/o impacting product's core functionality. The biggest benefi=
t with HXen is that it can be ported to any other OS without any changes to=
 the stable system.

With that goal, I wonder why you choose hxen (which is not
developed/maintained anymore, and has minimal or zero documentation)
instead of virtualbox (which is available under GPL except for the
extension pack, already supporting many host OS) or KVM (since you're
going to use Linux anyway), both are still actively developed.

Good luck though.

--=20
Fajar