Few build Hypervisors. We're one of them

virtualize.sh

15 points·plam503711··6 comments

I do wish people wouldn’t post their genetic marketing blog posts on here. Maybe write something interesting and detailed instead?

Hi, I’m the author of the blog post.

The goal wasn’t to dive deep into technical internals this time, but rather to share some perspective on what it actually takes to master an entire virtualization stack — especially after years of working only on the top layer (orchestration, backup, etc.). We’ve seen firsthand how much more complex things get the deeper you go.

That said, I totally get the desire for more technical content — and we’ve published more in-depth pieces before. For example, here’s a detailed post on Xen’s grant table mechanism and memory sharing, if that’s more your kind of read: https://xcp-ng.org/blog/2022/07/27/grant-table-in-xen/

Appreciate the feedback — and happy to go deeper on specific areas if there’s interest!

Btw, in your about page the link to Vates seems to be relative instead of absolute and directs to the wrong place (a subfolder in your domain instead of the Vates domain)

Nice catch! Fixing it now.

I don't really understand. I thought XCP-NG was using the Xen hypervisor.

That's because of the confusing names. Xen is not XenServer:

* Xen is the hypervisor, the "upstream" used by both XenServer & XCP-ng

* XenServer or XCP-ng is the platform, using Xen and various other things, to deliver a "turnkey" experience for server virtualization

Xen Project is part of the Linux foundation, and have various contributors, including AMD and Arm (for the embedded world) and others (including Vates, Citrix etc.)

Reply on news.ycombinator.com