xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Fajar A. Nugraha" <list@fajar.net>
To: "Deepak Kr. Sharma - ERS, HCL Tech" <deepak.s@hcl.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: FW: HXEN on linux
Date: Wed, 7 Sep 2011 20:56:12 +0700	[thread overview]
Message-ID: <CAG1y0sdQRMH64PHwz-UarFh6=UviphE1qGNjR+OLQpLSq2argg@mail.gmail.com> (raw)
In-Reply-To: <90F0F47595235141A4380FCF01B0185B2240FEADDE@CHN-HCLT-EVS07.HCLT.CORP.HCL.IN>

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 technology 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 one would want to touch a stable system (which is a must in case of type-1 hypervisor) for a value-add service. Hence, HXen gives flexibility to add features on VM w/o impacting product's core functionality. The biggest benefit 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.

-- 
Fajar

      reply	other threads:[~2011-09-07 13:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05  6:10 FW: HXEN on linux Deepak  Kr. Sharma - ERS, HCL Tech
2011-08-09 19:51 ` Konrad Rzeszutek Wilk
2011-08-10 11:27   ` Lars Kurth
2011-08-10 15:04     ` Konrad Rzeszutek Wilk
2011-08-25  7:15   ` Deepak  Kr. Sharma - ERS, HCL Tech
2011-08-25 14:24     ` Stefano Stabellini
2011-08-26 10:24       ` Deepak  Kr. Sharma - ERS, HCL Tech
2011-08-26 11:54         ` Tim Deegan
2011-08-26 12:07         ` Stefano Stabellini
2011-08-30  7:10           ` Deepak  Kr. Sharma - ERS, HCL Tech
2011-09-01 12:30           ` Deepak  Kr. Sharma - ERS, HCL Tech
2011-09-01 13:46             ` Konrad Rzeszutek Wilk
2011-09-05  7:13               ` Deepak  Kr. Sharma - ERS, HCL Tech
2011-09-06 16:12                 ` Konrad Rzeszutek Wilk
2011-09-07 12:19                   ` Deepak  Kr. Sharma - ERS, HCL Tech
2011-09-07 13:56                     ` Fajar A. Nugraha [this message]

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='CAG1y0sdQRMH64PHwz-UarFh6=UviphE1qGNjR+OLQpLSq2argg@mail.gmail.com' \
    --to=list@fajar.net \
    --cc=deepak.s@hcl.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).