Which virtualisation technology do you use on your Slack?
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I use Qemu on my file server for a couple VM servers I use for some special needs servers, stuff for work. On my desktop I use VirtualBox for just playing with random OS's and what not. They both work equally well for what I use them for. I have been thinking about trying out Xen though, heard some interesting things about it.
Currently I use VirtualBox OSE, as it is open source and an easy to set solution for desktop usage.
I used Qemu for some time, but it was very slow unless you used kqemu or KVM with it. kquemu has been killed, while KVM needs a processor able to handle it. I lack that processor. As of today, I don't think Qemu alone is a good idea if you want speed (it has been claimed that it provides better virtualization quality, so it might be of some use anyway).
Originally Posted by http://distrowatch.com/weekly.php?issue=20111017#news
The Linux kernel developers are tired of receiving bug reports relating to the VirtualBox module. When VirtualBox is installed on a Linux system the module "vboxdrv" is loaded into the kernel. According to Dave Jones' post to the Linux Kernel Mailing List this module contains too many bugs and causes too many problems. The module is open source, licensed under the GPL, but is not part of the kernel source code. Mr Jones has written a patch which will flag the VirtualBox module as being tainted. This will mean " automatic bug filing tools can opt out of automatically filing kernel bugs, and inform the user to file bugs somewhere more appropriate." Users experiencing problems related to the VirtualBox driver can visit that project's bugtracker to file a report.
I use VirtualBox myself but I tend to stick to the Closed Source version simply due to the fact my hardware uses a lot of things like USB 2.0 and such that the OSE doesn't support yet. Nothing for or against Oracle but I have to support my hardware properly.
I use VirtualBox on workstations.
The company uses VMWARE on servers, but I prefer to avoid it when I can.
In all cases (physical or virtual) I like using OpenVZ to add secure services and guest machines to Linux hosts.
I tried LXC for a few months, but it is simply not as robust or complete. Yet.
We have some MS Hyper in the company, but as near as I can tell it seems heavier, slower, and less mature than VMware.
It also REALLY BITES when you want Linux guests.
I tried the others, and find them heavier, slower, and wasteful, Generally more difficult to manage, and (in the case of the commercial products) priced beyond my limits.