Threads for doublej472

  1. 3

    If you’re interested in a less thorough HOWTO and more of a “this is what I built and what it lets me do” I recently documented my local VM setup atop Clear Linux + KVM. I’m less focused on HA and more on efficient use of resources, so there’s less automation around migration of workloads and more around de-duping storage and making the “fork” of a new VM easy.

    1. 1

      That was interesting to read! Using BTRFS + raw images sounds like it would work very well, since you can use native BTRFS compression and de-duplication to shrink and share data between VM storage drives, without having to worry about qcow2 base images. Maybe I need to change my VM storage filesystem from XFS to BTRFS…

      How stable has BTRFS been for you? I’ve had BTRFS lose my data multiple times in the past few years due to corruption, so I’m reluctant to use it for important files.

    1. 2

      Great write-up! I love “This is how I did it’ guides like this as they give me a flavor of what it’s like to actually work with a given piece of tech.

      1. 3

        Thank you! I wanted to write something that someone could follow on their own, and I tried to describe why I made certain choices, and gave examples of when you would want to make a difference choice (for example, whether you should enable STP on a network bridge). I’m glad you liked how it turned out!

      1. 3

        I wish more people would give Proxmox a chance. It’s a very capable hypervisor based on Debian with a decent web GUI.

        1. 4

          There are SO many hypervisors out there and everybody’s got a favorite horse in that race.

          1. 6

            The term ‘hypervisor’ has a very specific, narrow definition. Proxmox isn’t a hypervisor. In fact there are only a few hypervisors.

            Wow, the Wikipedia page on hypervisors is somewhat wrong.

            Looking at the “Classification” section, I would only call the “bare-metal” software listed there Hypervisors. bhyve and KVM are hypervisors, too, albeit weird fat ones.

            Here is an easy to highlight error in this wikipedia page: VirtualBox is not a hypervisor product, full stop. I don’t know when they started calling that kind of software a hypervisor, much less a “type-2”… Is this the result of some marketing strategy?

            Hypervisors run on bare metal. That’s part of the definition. VirtualBox is an application. (Albeit one that invokes some exotic CPU instructions…)

            1. 3

              This reminds me of the OS argument. Linux is not an OS it’s just a kernel. Ubuntu is not an OS either, it’s a distribution.

          2. 3

            xcp-ng1 is also pretty cool

            1. 1

              I haven’t tried using Proxmox at all yet, but I definitely want to! The web GUI does look pretty nice.

              1. 2

                We use it at work, after switching from VMWare. Medium-small company, we use it to manage telephony and networking servers/clusters. The sysadmins seem to love it.