Dear all,
I certainly do not want to start a type 1 vs type 2 holly war. But I'm
working on some introductory course on virtualization and I have hard
time to conciliate the average user daily experience with the premise
KVM *is* type 1.
More precisely, I've read KVM turns the Linux kernel into a type 1
hypervisor. I can understand that. However, from the user perspective,
when running Linux with KVM, you can still launch process _outside_ any
guest. Something I could represent like that:
+----------+----------+
| app B | app C |
+----------+----------+
| guest OS | guest OS |
+----------+----------+----------+
| app A | QEMU/KVM | QEMU/KVM |
+--------------------------------+
| Linux/KVM |
+--------------------------------+
| HW |
+--------------------------------+
With that model, "app A" _seems_ to be running directly "on the host".
And to be honest, it furiously reminds me the typical model for a type 2
hypervisor.
Or are we considering "app A" is running in its own "hidden" VM,
something like the dom0 in Xen?
--
-- Sylvain Leroux
-- sylvain@xxxxxxxxxxx
-- http://www.chicoree.fr
Attachment:
signature.asc
Description: OpenPGP digital signature
