virt-manager VS HomeBrew

It's still being updated. I don't see anything on the virt-manager homepage or GitHub that would suggest it is deprecated.

https://virt-manager.org/

https://github.com/virt-manager/virt-manager

It can't do literally everything Qemu/libvirt can do using only the UI, but given that it has escape hatches to directly edit libvirt configurations, and libvirt has escape hatches to directly pass arguments to Qemu, there's very little you can't do with it.

I would love to see a serious comparison (features & performance) between VMWare ESXi, Proxmox VE and let's say a more stock RHEL or Ubuntu. And maybe even include FreeBSD/bhyve.

Because yes, in terms of core functionality it should be in the same ballpark. And in terms of UI, Virtual Machine Manager [0] was not that bad.

[0] https://virt-manager.org/

Shout out to https://virt-manager.org/ - works much better for me, supports running qemu on remote systems via ssh. I used to use this all the time for managing bunches of disparate vm hosts and local vms.

If not, I would just run a CentOS Stream 8 virtual machine using either GNOME Boxes or virt-manager, and set up networking and ssh so you can access the database from the host.

https://virt-manager.org/ <- Recommend this as Front-end

I'd say it is half-baked webmin. You can only use it with NetworkManager, and if you have an even remotely complex network setup for VMs, NetworkManager usually must be turned off, which makes Cockpit practically unusable. virt-manager [1] is way more powerful for those who like managing VMs with GUI.

[1] https://virt-manager.org/

$ apt build-dep libvirt $ git clone https://github.com/libvirt/libvirt.git Cloning into 'libvirt'... $ cd libvirt $ meson setup build $ ninja -C build $ ninja -C build install $ which virsh /usr/local/bin/virsh $ which libvirtd /usr/local/sbin/libvirtd $ apt install libgtk-3-dev libpulse-dev libgbm-dev libspice-protocol-dev \ libspice-server-dev libusb-1.0-0-dev libepoxy-dev libfdt-dev $ git clone -b v5.1.0 http://git.qemu.org/qemu.git $ cd qemu-v5.1.0 $ git submodule add -f https://git.kernel.org/pub/scm/utils/dtc/dtc.git dtc $ ./configure --disable-werror --target-list=arm-softmmu \ --enable-opengl --enable-gtk --enable-kvm --enable-guest-agent \ --enable-spice --audio-drv-list="oss pa" --enable-libusb \ --enable-trace-backend=simple --enable-debug $ make $ make install $ git clone https://github.com/virt-manager/virt-manager.git $ apt install gobject-introspection libosinfo-1.0-0 libosinfo-1.0-dev \ gir1.2-libosinfo-1.0 libvirt-glib-1.0-dev $ cd virt-manager $ ./setup.py configure --prefix=/usr/local $ sudo ./setup.py install $ sudo usermod -a -G libvirt root $ sudo usermod -a -G libvirtd root $ sudo usermod -a -G libvirt-qemu libvirt-qemu $ sudo usermod -a -G libvirt marietto $ sudo adduser libvirt-qemu $ sudo groupadd --system libvirt $ sudo groupadd --system libvirt-qemu $ sudo newgrp libvirt-qemu $ newgrp libvirt $ /usr/local/sbin# libvirtd & [1] 2875 $ /usr/local/sbin# virtqemud & info : libvirt version: 9.7.0 info : hostname: chromarietto error : virPidFileAcquirePathFull:409 Failed to acquire pid file : /var/local/run/libvirt/qemu/driver.pid Resource temporarily unavailable error : virStateInitialize:672 : Initialization of QEMU state driver failed Failed to acquire pid file : /var/local/run/libvirt/qemu/driver.pid Resource temporarily unavailable error : daemonRunStateInit:617 : Driver state initialization failed $ /usr/local/sbin# ps ax | grep libvirt 2875 pts/0 Sl 0:00 libvirtd $ /usr/local/sbin# ps ax | grep virtqemu nothing If I do the opposite way : $ /usr/local/sbin# virtqemud & $ /usr/local/sbin# ps ax | grep virtqemu 3041 pts/0 Sl 0:00 virtqemud $ /usr/local/sbin# libvirtd & info : libvirt version: 9.7.0 info : hostname: chromarietto error : virPidFileAcquirePathFull:409 Failed to acquire pid file : /var/local/run/libvirt/qemu/driver.pid Resource temporarily unavailable virStateInitialize:672 : Initialization of QEMU state driver failed Failed to acquire pid file : /var/local/run/libvirt/qemu/driver.pid Resource temporarily unavailable daemon RunStateInit:617 : Driver state initialization failed $ /usr/local/sbin# ps ax | grep virtqemu 3041 pts/0 Sl 0:00 virtqemud $ /usr/local/sbin# ps ax | grep libvirt nothing

I want to test Hyprland with NixOS in a VM using Virt-Manager (https://virt-manager.org/) on Arch Linux host before installing it on my machine.

Homebrew is a highly popular package manager on macOS and Linux systems, enabling users to easily install, update, and uninstall command-line tools and applications. Its design philosophy focuses on simplifying the software installation process on macOS, eliminating the need for manual downloads and compilations of software packages.

Homebrew - package manager for linux-based OSs.

Package Manager: Homebrew

Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.

Are you using SQLite that ships with macOS, or SQLite installed from homebrew?

I had a different problem in the past with the SQLite that ships with macOS, and have been using SQLite from homebrew since.

So if it’s the one that comes with macOS that gives you this problem that you are having, try using SQLite from homebrew instead.

https://brew.sh/

Before we begin, make sure you have Homebrew installed on your Mac. Homebrew is a package manager that makes it easy to install software and dependencies. You can install Homebrew by following the instructions on their website: https://brew.sh/

I’m on MacOS and erlang.org, elixir-lang.org, and postgresql.org all suggest installation via Homebrew, which is a very popular package manager for MacOS.

I have always either installed Node from the installer provided by the Nodejs website or, via Brew in macOS. I have also used nvm in the past but did not know that there was a best practice to guide us.

A running Rails application needs a database to connect to. You may already have your database of choice installed, but if not, I recommend PostgreSQL, or Postgres for short. On a Mac, probably the easiest way to install it is with Posrgres.app. Another option, the one I prefer, is to use Homebrew. With Homebrew installed, this command will install PostgreSQL version 16 along with libpq:

On a macOS machine, you can use homebrew by running the command.