On Tue, Aug 15, 2017 at 2:10 PM, Rich Freeman <[email protected]> wrote: > On Tue, Aug 15, 2017 at 3:02 PM, R0b0t1 <[email protected]> wrote: >> On Tue, Aug 15, 2017 at 12:00 PM, Hartmut Figge <[email protected]> wrote: >>> Helmut Jarausch: >>> >>>>I'm running linux-4.12.7-gentoo with Virtualbox >>>>BUT you need app-emulation/virtualbox and Co in version 5.1.26 >>> >>> Hm. My Gentoo is mostly stable. That would mean to add virtualbox to the >>> unstable part. Hm. >>> >> >> On Gentoo I have found it fairly normal to switch to unstable (or >> unkeyworded) packages to fix issues. >> >> I don't want to change the subject too much, but I've fond QEMU a >> decent replacement for VirtualBox. It takes some set up at first but >> is fairly rewarding and easy to manage. I don't suggest using libvirt >> on Gentoo, but some people do. The main difference with not using >> libvirt, besides managing QEMU flags and VM startup yourself, is that >> spice doesn't work (the non-libvirt spice viewer has longstanding >> bugs, namely a particularly annoying one related to being unable to >> exit out of fullscreen mode). Depending on your usecase setting up >> remote access from within the OS of your VM might give you a better >> experience - you might even try that if you continue using VirtualBox. >> > > Another option is KVM.
I'd like to interject for a moment. What you're referring to as KVM, is, in fact, QEMU/KVM, or as I've recently taken to calling it, QEMU plus KVM. KVM is not a virtualization solution unto itself, but rather another free component of a fully functioning FOSS virtualization system made useful by a hypervisor, interface, and device emulation components comprising a full virtualization system as defined by nobody.[1] Admittedly I referred to only QEMU above. > I do suggest using libvirt, and found that > app-emulation/virt-manager gives you a lot of the benefits of > something with a pretty GUI like Virtualbox, but it is 100% FOSS > underneath and you can run it all from the command line too. It is > just a front-end to libvirt. There are no issues with running these > VMs as services also, and I believe that you can connect to their > consoles at any time with virt-manager. > My only issue is that when I used libvirt I had to edit the produced configurations by hand, and the settings wouldn't always take. Certain hardware configurations were also hard to set up. However, should everything work it is very nice, and can do things like start your VMs on boot and create tap devices on demand, etc. R0b0t1. [1] https://www.gnu.org/gnu/linux-and-gnu.html
