Discussion
From Proxmox to FreeBSD and Sylve in Our Office Lab | IP Technics | Dubai
gcifuentes: Bhyve doesn't feature nested virt though.
sidkshatriya: I love FreeBSD but Linux just provides every feature under the sun when it comes to virtualization. Do you find any missing features on bhyve ? Is bhyve reliable ? I can't imagine its been tested as thoroughly as KVM ...
gcifuentes: Bhyve is quite cool but no nested virt which means you cannot nest vm_enter/exit calls with EPT pages so you cannot virtualize within those guests. I found this crucial. For instance Qubes OS won't run in Bhyve by any means.
seanw444: Do they have any near-future plans to resolve that?
rwmj: Or Windows VBS, if you need to run full-featured Windows VMs.
KaiserPro: What does Sylve provide that proxmox doesn't?Or better, how does it do it better than proxmox?This isn't to say that proxmox is the best thing since sliced bread, I'm curious as to what makes sylve better, is it the API?
evanjrowley: Without looking at the Sylve docs, I'll conjecture that it has deeper integration with ZFS. With a foundation on FreeBSD, there is a likelihood Sylve can support ZFS-on-root rollbacks better than hacking it into Proxmox. A rollback capability is why I'm looking for Proxmox alternatives. Both Talos Linux and IncusOS provide A/B updates which achieve a similar rollback capability. With something based on FreeBSD, your "immutable" OS and all of it's data can be treated equally as ZFS datasets.
MisterTea: If you are unsure of bhyve's abilities then why not test yourself? Speculation and guessing about stability or testing is useless without seeing if it works in your application.
dizhn: Sylve looks like a decent project with a promising future but this article really doesn't explain why they picked it over Proxmox at all. They explain a lot of things but I can't see the advantage over prox other than they wanted to use it.
sidkshatriya: > If you are unsure of bhyve's abilities then why not test yourself?It is not possible to come to a conclusion about everything in the world yourself. No one has the time to try out everything themselves. It could mean tremendous amounts of time wasted.That is why you ask for recommendations of hotels, restaurants, travel destinations, good computer brands, software and so on from friends, relatives or other trusted parties/groups.HN is actually the perfect place to ask for opinions. Someone just said bhyve does not support nested virtualization (useful input !). Someone else might chime in and say they have run bhyve for a long time and they trust it (and so on...)So I can't agree with your viewpoint.
Cyph0n: Sometimes unification can be an advantage.I run Proxmox at home, but now that I have been drinking the NixOS koolaid over the past 2 years, all of my homelab problems suddenly look like Nix-shaped nails.
dizhn: I have the same thing with proxmox especially after I realized how well it integrates with proxmox backup server. And I haven't even gotten into clustering yet. It really is a very solid product.
Cyph0n: Indeed, Proxmox VE is an amazing product.
EnigmaCurry: Same. Here's how I scratch the NixOS itch on Proxmox and/or libvirt[1]. One interface for both targets.[1] https://github.com/EnigmaCurry/nixos-vm-template
dizhn: That feature list looks really good. It would actually be really nice to standardize the guest operating systems in such a way.
justsomehnguy: > Sylve can support ZFS-on-root rollbacks better than hacking it into ProxmoCan you explain your use case when you absolutely can't provide a separate M.2 drive solely for the OS?
evanjrowley: Regardless of the number of drives available, you gain an advantage when your file system can leverage snapshots to roll backwards or forwards. There are other Linux-native filesystems that can provide this capability too, but many admins prefer ZFS because the full range of capabilities is unparelleled.