6
submitted 2 months ago by buedi@feddit.org to c/selfhosted@lemmy.world

I spent a few days comparing various Hypervisors under the same workload and on the same hardware. This is a very specific workload and results might be different when testing oher workloads.

I wanted to share it here, because many of us run very modest Hardware and getting the most out of it is probably something others are interested in, too. I wanted to share it also because maybe someone finds a flaw in the configurations I ran, which might boost things up.

If you do not want to go to the post / read all of that, the very quick summary is, that XCP-ng was the quickest and KVM the slowest. There is also a summary at the bottom of the post with some graphs if that interests you. For everyone else who reads the whole post, I hope it gives some useful insights for your self-hosting endeavours.

top 8 comments
sorted by: hot top controversial new old
[-] undu@discuss.tchncs.de 2 points 2 months ago

Xcp-ng might have the edge against bare metal because Windows uses virtualization by default uses Virtualization-Based Security (VBS). Under xcp-ng it can't use that since nested virtualization can't be enabled.

Disclaimer: I'm a maintainer of the control plane used by xcp-ng

[-] buedi@feddit.org 1 points 2 months ago

Oooh, that explains it! I wondered what is going on. Thank you very much. And thank you for working on XCP-ng, it is a fantastic platform :-)

[-] Appoxo@lemmy.dbzer0.com 0 points 2 months ago

What I am missing is ESXi/vSphere. Would be quite important for the few people that have access to the eval ressources to set it up.
Same for the BSD versions. I think Beehive?

[-] buedi@feddit.org 1 points 2 months ago

Sure, ESXi would have been interesting. I thought about that, but I did not test it because it is not interesting to me anymore from a business perspective. And I am not keen of using it in my Homelab, so I left that out and use that time to do something relaxing. It's my holiday right now :-)

[-] node815@lemmy.world 0 points 2 months ago

I discovered about a few months ago that XCP-NG does not support NFS shares which was a huge dealbreaker for me. Additionally, my notes from my last test indicated that I could not mount existing drives without erasing them. I'm aware that I could have spun up a TrueNAS or other file sharing server to bypass this, but maybe not if the system won't mount the drives in the first place so it can pass them to the TrueNAS . I also had issues with their xen-orchestra which I will talk about below shortly. They also at the time, used an out of date CentOS build which unless I'm missing something, is no longer supported under that branding.

For the one test I did which was for a KVM setup, was my Home Assistant installation, I have that running in Proxmox and ccomparativelyit did seem to run faster than my Proxmox instance does. But that may be attributed to Home Assistant being the sole KVM on the system and no other services running (Aside from XCP-NG's).

Their Xen-Orchestra for me was a bit frustrating to install as well, and being locked behind a 14 day trial for some of the services was a drawback for me. They are working on the front end gui to negate the need for this I believe, but the last time I tried to get things to work, it didn't let me access it.

[-] turnip@sh.itjust.works 0 points 2 months ago

What do you use NFS for, isn't NFS relatively obsolete by now?

Assume I know not much about file shares.

[-] Appoxo@lemmy.dbzer0.com 1 points 2 weeks ago

Sorry for reviving this comment.

How do you connect to network shares in your environment? SMB?

[-] node815@lemmy.world 1 points 2 months ago

NFS4 I don't think its obsolete.

I use it for my Desktop computers to connect to the server. All of my systems use Linux so that's my primary use. They backup to the server nightly.

this post was submitted on 07 Mar 2025
6 points (100.0% liked)

Selfhosted

47043 readers
261 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS