xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Oleksii Kurochko <oleksii.kurochko@gmail.com>
Cc: talex5@gmail.com, Wei Liu <wei.liu2@citrix.com>,
	ian.campbell@citrix.com, xen-devel@lists.xen.org
Subject: Re: Mini-OS as Dom0
Date: Tue, 23 Feb 2016 18:03:15 +0000	[thread overview]
Message-ID: <20160223180315.GB23681@citrix.com> (raw)
In-Reply-To: <CAMacjJzs9jVqk_9rHRNHzD7ccfFpERdpjwkrfp9C66a9WHHx5A@mail.gmail.com>

On Tue, Feb 23, 2016 at 07:38:15PM +0200, Oleksii Kurochko wrote:
> Hello.
> 
> Any updates?
> 
> With best regards,
>  Oleksii
> 
> 2016-02-09 14:23 GMT+02:00 Oleksii Kurochko <oleksii.kurochko@gmail.com>:
> 
> > Hello.
> >
> > I want to use Mini-OS as Dom0.
> >
> > What should be done for this purpose?
> > Someone tried to do something like that? Maybe there are some patches.
> >

This is a really bold idea.  I don't think anybody ever tries that.

Let me explain. In a typical setup, Dom0 has many roles. It drives real
hardware, it runs emulation (QEMU) for guest if necessary, it provides
PV backends, and it also runs the toolstack for managing the whole
platform.

Depending on what you want to achieve, the workload to support the
functionality of your choice varies. But I'm sure it is going to be
significant even if you pick the easiest one.

Wei.

> > With best regards,
> >  Oleksii
> >

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

      reply	other threads:[~2016-02-23 18:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 12:23 Mini-OS as Dom0 Oleksii Kurochko
2016-02-23 17:38 ` Oleksii Kurochko
2016-02-23 18:03   ` Wei Liu [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=20160223180315.GB23681@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=oleksii.kurochko@gmail.com \
    --cc=talex5@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /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).