Current64 - Kernel 5.8 - KVM vs VirtualBox & Vmware
I am an avid VirtualBox user -- my use case being running/testing liveCDs such as my (private) Current64-based fork of PartedMagic.
Kernel 5.8 seems to be a problem for Virtualbox (https://www.virtualbox.org/ticket/19644) as well as VMware (http://rglinuxtech.com/?p=2774). Therefore (and as I do from time to time) I had a look at KVM/Qemu. I found a qemu package by AlienBob (http://slackware.uk/people/alien/slackbuilds/) as well as one by Conraid (http://slack.conraid.net/repository/...are64-current/). AlienBob has no packages for libvirt or virt-manager, but Conraid has. Defining/running a simple VM under AlienBob's qemu together with Conraid's libvirt and virt-manager gave a lot of "hardware" problems. Doing so with Conraid's qemu, libvirt and virt-manager was more successful (after a lot of failures - I found things to be less user-friendly than I am used to). Booting my ISO under KVM/Qemu takes longer than under VirtualBox (40 vs 23 seconds). Afterwards both implementations seem to perform comparably. Google tells me that Gnome Boxes is the next thing after virt-manager. Alas I could not find a package or slackbuild to test things. Anyone willing to share his/her experiences? :D |
I used ponce's SBo-git repository exclusively to build virt-manager and virt-viewer under current. No issues. See below for my build tree with comments. A number of packages have been added to current since I first went down this path. Also, I installed the deps one-by-one instead of using sqg so that I wouldn't miss anything during the build process.
Code:
gtksourceview3 |
All times are GMT -5. The time now is 09:52 PM. |