Helpful link for people new to virtualization

I was hanging out with my good friend, Mr Googles, who gave me a basic explanation of the different virtualization techniques commonly in use today.
It even has an nice graphic to help keep things straight.

I'll have to call shenanigans on that link.

It incorrectly indicates that KVM is not a Hypervisor but from the Wikipedia page we see:

KVM (Kernel-based Virtual Machine) is a virtualization infrastructure for the Linux kernel which turns it into a hypervisor.

.

It also incorrectly indicates MS HyperV as not being a full OS installation like a KVM system. Also VMWare IS a full OS installation but it IS also customized for virtualization. (In fact in early VMWare boots the only noticeable difference between the initial boot screens on it and the RHEL version it seems clearly derived from is the name it shows during the boot.)

Saying XEN doesn't require OS installation is also silly - the original Xen installs I saw were on top of RHEL.

It's nice to try to simplify things but that chart in my view is way off.

KVM is a hypervisor, the beauty of it is that it doesn't, like Xen/hyper-v or the new versions of vmware, require dual kernel systems, but shares the single kernel between the hosts and guests. It is more efficient, and this, better, architecture is the only one out there really alowing for some amazing performance none of the other hypervisors are capable of.

To better understand the beauty of the design, look at the graphics here: http://chucknology.com/2012/02/02/kv...ux-xen-is-not/

You probably don't realize this but most of these people think the Hypervisor is the thing that lets you look a the guests desktop, and I'm talking about RHEL certified admins here, not "newbies".
If you have a better way to help new people begin to conceptualize virtualization and emulator stacks, I think there is a critical need for tutorials here at Linuxquestions.org and if you manage to put together something that a moderately technical person can understand, I'll reference it everywhere I go on the internet where I think it might be of help to people.
But it has to be simple to understand. Use the 14 year old test. If your average 14 year old can't read it and understand most of it, you're not going to peak any ones interest sufficiently to get them to invest the time to understand the basics, at which point the entire "Your Hypervisor isn't the thing that lets you watch Netflix on the guest", conversation will make a whole lot more sense to them.
You may have noticed we have an awful lot of anonymous guests on this forum, I'd imagine they represent a significant number of people who've heard of virtualization but don't really understand it.
This post was for them to help them get started, to show them that it all isn't as incomprehensible as it might at first appear to be.

I'll have to call shenanigans on that link

You chose to call shenanigans on that link because it was low hanging fruit, Don't kid yourself.

I "called shenanigans on it" as an amusing (to me at least) reference to South Park but then explained why I felt it wasn't a good depiction of virtualization.

Explaining things to your average 14 year old by giving them misinformation like that contained in the link is a good way to have them tune you out.

Much of the reason some of the teens in my generation moved on to hard drugs despite the inherent dangers in same was because we were fed obvious BS about the dangers of Marijuana and Alcohol in "health" classes. To be sure there are dangers in any drugs but equating marijuana use with heroin and cocaine use was a bad idea. If you tried the former and didn't experience the extreme effects ascribed to it you were more willing to believe (incorrectly) that the latter two weren't as bad as they said.