Hi,
Anyone using KVM (Kernel-based Virtual Machine) ?
Yes, I have deployed KVM VMs since c. 2009 (initially wrote bash scripts for each VM); used virt-manager and virsh later on. And now I plan to use Proxmox VE for KVM VMs.
How does it compare to VirtualBox and/or Proxmox?
VirtualBox v/s KVM -- IMO, they are an apple and an orange. VB is a desktop app with its own network and storage drivers that load as kernel modules plus it provides sound and USB support. VB can leverage hardware acceleration (KVM). Whereas, KVM is Linux kernel native and more appropriate for a server setup. I use VB a lot to evaluate software, test use cases, and then migrate the VM to KVM server for production usage. You can also launch VB VMs (headless) for server apps on your desktop, make sure the VM NIC is bridged to the desktop NIC/WiFi and is configured as a DHCP client. On the DHCP server, you can program the VM's NIC MAC address to a fixed IP address. (see 'vboxmanage help' for a synopsis of the possibilities)
VB v/s ProxmoxVE (see above). Proxmox (Debian-based) is essentially KVM with a very functional and easy-to-use Web UI.
IMO, it is n00b friendly and can be set up on a repurposed thin client (8GB RAM/128 GB storage) or as a VB VM*; a quick and easy way to get your hands wet with the product. It is well documented and the user forum is very helpful.
* Here is the power of both tools -- Most modern CPUs support *nested* virtualization; you need to turn it ON (Google it).
I evaluated Proxmox VE as a VB VM and spun up a couple of small VMs within the Proxmov VE 🖖
The bottom line -- both VB and Proxmox (KVM) are very powerful, you need to figure out your use case and pick the appropriate platform.
HTH
--
Arun