On Mon, Aug 24, 2020 at 9:48 AM Michael <[email protected]> wrote: > > On Monday, 24 August 2020 13:02:56 BST Rich Freeman wrote: > I may give virt-manager a spin, because the users will require a GUI manager > to launch VMs, but then if I start emerging packages at large I could emerge > VBox from source instead. On my personal machine I just run QEMU, but I find > plugin/unplugin USBs and other hardware via the QEMU monitor console to be > rather clunky. I've stayed with QEMU over the years as a more minimalist > solution. I preferred it as a more direct and simple solution to multiple > virt layers, APIs and what not.
Yeah, it is a little more complex. Also, it is linux-only. However, it is libvirt under the hood which means a lot of other stuff is compatible with it. If you're just running traditional images in a directory somewhere it is pretty easy to set up. One advantage of VirtualBox is that you can run the same VM on Windows as well. > > I'll also note that 95% of the time when you're using a VM running > > Linux you're probably better-off using a container. > > I use QEMU to run full virtual OSs - MSWindows, Android, other Linux distros. > A container wouldn't do this You can run other linux distros in a container, minus the kernel. Many of my containers are non-Gentoo on a Gentoo host. Since kernel compatibility is very robust it generally isn't an issue to not run one tailored to the distro. Containers are popular enough that most distros have some sort of container root tarball available. -- Rich
