With free esxi over, not shocking bit sad, I am now about to move away from a virtualisation platform i’ve used for a quarter of a century.

Never having really tried the alternatives, is there anything that looks and feels like esxi out there?

I don’t have anything exceptional I host, I don’t need production quality for myself but in all seriousness what we run at home end up at work at some point so there’s that aspect too.

Thanks for your input!

  • @anamethatisnt@lemmy.world
    link
    fedilink
    English
    100
    edit-2
    1 year ago
    • KVM/QEMU/Libvirt/virt-manager on a Debian 12 for minimal installation that allows you to choose backup tools and the like on your own.
    • Proxmox for a mature KVM-based virtualizer with built in tools for backups, clustering, etcetera. Also supports LXC. https://github.com/proxmox
    • Incus for LXC/KVM virtualization - younger solution than Proxmox and more focused on LXC. https://github.com/lxc/incus
    • @vegetaaaaaaa@lemmy.world
      link
      fedilink
      English
      16
      edit-2
      1 year ago

      /thread

      This is my go-to setup.

      I try to stick with libvirt/virsh when I don’t need any graphical interface (integrates beautifully with ansible [1]), or when I don’t need clustering/HA (libvirt does support “clustering” at least in some capability, you can live migrate VMs between hosts, manage remote hypervisors from virsh/virt-manager, etc). On development/lab desktops I bolt virt-manager on top so I have the exact same setup as my production setup, with a nice added GUI. I heard that cockpit could be used as a web interface but have never tried it.

      Proxmox on more complex setups (I try to manage it using ansible/the API as much as possible, but the web UI is a nice touch for one-shot operations).

      Re incus: I don’t know for sure yet. I have an old LXD setup at work that I’d like to migrate to something else, but I figured that since both libvirt and proxmox support management of LXC containers, I might as well consolidate and use one of these instead.

      • @anamethatisnt@lemmy.world
        link
        fedilink
        English
        101 year ago

        I use cockpit and my phone to start my virtual fedora, which has pcie passthrough on gpu and a usb controller.

        Desktop:

        Mobile:

        • @Voroxpete@sh.itjust.works
          link
          fedilink
          English
          61 year ago

          We use cockpit at work. It’s OK, but it definitely feels limited compared to Proxmox or Xen Orchestra.

          Red Hat’s focus is really on Openstack, but that’s more of a cloud virtualization platform, so not all that well suited for home use. It’s a shame because I really like Cockpit as a platform. It just needs a little love in terms of things like the graphical console and editing virtual machine resources.

      • SayCyberOnceMore
        link
        fedilink
        English
        51 year ago

        Ooh, didn’t know libvirt supported clusters and live migrations…

        I’ve just setup Proxmox, but as it’s Debian based and I run Arch everywhere else, then maybe I could try that… thanks!

        • @vegetaaaaaaa@lemmy.world
          link
          fedilink
          English
          6
          edit-2
          1 year ago

          In my experience and for my mostly basic needs, major differences between libvirt and proxmox:

          • The “clustering” in libvirt is very limited (no HA, automatic fencing, ceph inegration, etc. at least out-of-the box), I basically use it to 1. admin multiple libvirt hypervisors from a single libvirt/virt-manager instance 2. migrate VMs between instances (they need to be using shared storage for disks, etc), but it covers 90% of my use cases.
          • On proxmox hosts I let proxmox manage the firewall, on libvirt hosts I manage it through firewalld like any other server (+ libvirt/qemu hooks for port forwarding).
          • On proxmox I use the built-in template feature to provision new VMs from a template, on libvirt I do a mix of virt-clone and virt-sysprep.
          • On libvirt I use virt-install and a Debian preseed.cfg to provision new templates, on proxmox I do it… well… manually. But both support cloud-init based provisioning so I might standardize to that in the future (and ditch templates)
              • @mlaga97@lemmy.mlaga97.space
                link
                fedilink
                English
                11 year ago

                Pretty darn well. I actually needed to do some maintenance on the server earlier today so I just migrated all of the VMs over to my desktop, did the server maintenance, and then moved the VMs back over to the server, all while live and functioning. Running ping in the background looks like it missed a handful of pings as the switches figured their life out and then was right back where they were; not even long enough for uptime-kuma to notice.

            • @vegetaaaaaaa@lemmy.world
              link
              fedilink
              English
              2
              edit-2
              1 year ago

              clustering != HA

              The “clustering” in libvirt is limited to remote controlling multiple nodes, and migrating hosts between them. To get the High Availability part you need to set it up through other means, e.g. pacemaker and a bunch of scripts.

    • @garibaldi@startrek.website
      link
      fedilink
      English
      31 year ago

      This is what I would recommend too - QEMU + libvirt with Sanoid for automatic snapshot management. Incus is also a solid option too