[TZubiri]

It's one of those topics, that's so modern and based around ecosystem specifics, that you are better off learning from manufacturer manuals and source code, rather than academic theory books.

Like, uni books won't give you an x86 manual because that wouldn't be neutral, but that's precisely the foundation of virtualization, from both a host and guest perspective.

You can read books on x86, but why not use some official intel manual?

[wmf]

I find many manuals miss the big picture. Maybe read the VMware, Xen, and KVM papers first.

[TZubiri]

Oh for sure, you are seeing the small pictures, but those are objective facts.

Big picture for virtualization? There's many, it's a complex emerging phenomenon which placed a lot of asterisks on computation, is it used for security? Or to patch tech debt? or to provide backwards compatibility? Yes. What is the limit between isolation and efficiency? No one knows yet and there's many answers, you can activate shared cpu caching or disable Spectre mitigations for efficiency, or you can just forego virtualization as a whole and depend on application level multitenancy, which is not a separate topic at all in terms of virtualization, as you can see with tech like containers, and t1/t2 hybrids, it's a spectrum of virtualization, there is no hard line separating the virtualized from the bare metal.

[naasking]

The first hypervisors were microkernels like L4. All of the fundamentals are in microkernel literature which stretches back to the 80s, though I don't think there's a need to read anything before L4 in the 90s.