From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
quizyjones <quizy_jones@outlook.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: what's the type of nested xen? HVM or PV?
Date: Mon, 4 Jan 2016 13:18:22 +0000 [thread overview]
Message-ID: <1451913502.13361.86.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1601041247050.19710@kaball.uk.xensource.com>
On Mon, 2016-01-04 at 12:52 +0000, Stefano Stabellini wrote:
> On Thu, 24 Dec 2015, quizyjones wrote:
> > Happy Holiday, guys. God tell me that I should work this out before
> > celebrate ; )I create a HVM first, then
> > compile Xen on it. The dom0 of this Xen is a PV. So is this nested xen
> > a HVM or a PV? It's hard to differentiate
> > when concerning to enable events as only HVM supports events.
>
> Xen itself, the hypervisor, is neither HVM or PV. HVM and PV are types
> of virtual machines; the distinction doesn't apply to the hypervisor.
I think it's a little more subtle (AKA complicated) than that.
The L1 Xen is running "bare metal" inside what L0 Xen sees as an HVM guest.
However the L1 Dom0 is running PV, but it is PV WRT the L1 Xen, not the L0
Xen. From the L0's point of view the combination of L0 Xen+Dom0 remains
HVM.
In fact the PV L1 Dom0 might even be able to see some "PVHVM" like aspects
of the L0 HVM domain in which it is running, although typical
configurations don't (or can't) make use of that.
I'm not sure what the original "enable events" is referring to, so I'm not
sure whether this has clarified anything or not.
Ian.
prev parent reply other threads:[~2016-01-04 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 13:02 what's the type of nested xen? HVM or PV? quizyjones
2016-01-04 12:52 ` Stefano Stabellini
2016-01-04 13:18 ` Ian Campbell [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=1451913502.13361.86.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=quizy_jones@outlook.com \
--cc=stefano.stabellini@eu.citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.