kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: sylvain@chicoree.fr
Cc: kvm@vger.kernel.org
Subject: Re: KVM is type 1 hypervisor, but...
Date: Mon, 29 May 2017 01:13:23 -0700	[thread overview]
Message-ID: <20170529081323.GB25630@infradead.org> (raw)
In-Reply-To: <48902d71-d540-4cd6-b76b-196febf40db6@email.android.com>

I never understood why people cared about it too much,  the terms come
from a academic paper in the 70s and we're even fully correct back
then, and have gotten less an less useful.

To make some sense of them it might be better to understand them in
terms of use cases rather than implementation, e.g. in terms of
KVM someone running a VM or two in addition to a normal desktop Linux
(e.g. a kernel developer testing things, or a Windows VM for a certain
application) fits into the type 2 model, while a server whos primary
purpose is to host VMs it type 1.  But with todays cloud or
hyperconverged architectures a single host system very often runs
VM and actualy workloads (e.g. storage backends or databases) as well.

So in my eyes it's a very theoretical concept that doesn't have any
practical relevance.

  parent reply	other threads:[~2017-05-29  8:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-27 17:06 KVM is type 1 hypervisor, but Sylvain Leroux
2017-05-28  6:34 ` Christoph Hellwig
2017-05-28  8:46   ` Sylvain Leroux
2017-05-28 11:51     ` Christoph Hellwig
2017-05-28 19:06       ` Sylvain Leroux
2017-05-29  6:41         ` Jan Kiszka
2017-05-29  9:05           ` Sylvain Leroux
2017-05-29 20:34             ` Jan Kiszka
2017-06-05 15:00               ` Sylvain Leroux
     [not found]       ` <48902d71-d540-4cd6-b76b-196febf40db6@email.android.com>
2017-05-29  8:13         ` Christoph Hellwig [this message]
2017-05-29  9:12           ` Sylvain Leroux
2017-05-30 13:16 ` Paolo Bonzini
     [not found]   ` <CACJDEmor4xvd4t2cEW=MLJrQiwQP9rpON09CLXDouw_Oej3Cng@mail.gmail.com>
2017-05-31 14:21     ` Paolo Bonzini
2017-06-05 14:39   ` Sylvain Leroux
2017-06-05 15:40     ` Paolo Bonzini

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=20170529081323.GB25630@infradead.org \
    --to=hch@infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=sylvain@chicoree.fr \
    /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).