SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Virtualbox does not need a GUI. I use Virtualbox headless all the time. Check out the "VBoxHeadless" and "VBoxManage" commands. There was a recent article on howtoforge, IIRC, about this as well.
The article was written with CentOS in mind, but the VirtualBox commands the author goes through of course would work on any distro including Slackware.
Last edited by chess; 05-10-2010 at 03:19 PM.
Reason: add article link
So, which typically runs faster, VirtualBox, Qemu or KVM?
(I'm running apache, mail and fileserving with samba...)
Please note that Qemu is the userspace part of the KVM package; and I believe Qemu technology can be found in VBox as well.
I can't vouch for VBox but I can tell you I can have up to 15-20 users accessing a Debian Samba server running a KVM Windows 2003 terminal services VM and they don't suspect a damn thing. Speed is blinding; and I haven't had that server blink on me once in two and a half years.
Not once.
It was my first VM setup and pretty much my first serious Linux server. KVM won't let you down. I run my own VMs here and I can have three or four Linux/BSD/MS virtual machines open at a time. Speed is native. The only thing I hear people complain about regarding KVM is its relatively poor graphics performance but on a server with no X that's not going to affect you.
If I were setting up that server now I would use Slackware and KVM without hesitation. There is a Slackbuild for KVM/Qemu.
I compiled packages for VirtualBox and then decided to give KVM a try based on you guys but, I've hit a snag.
My test box is old and does not have BIOS Virtualization. Does anyone have instructions/a link to how to set up QEMU/KVM on boxes without BIOS Virtualization? I was reading through the QEMU wiki and apparently, it will run without the virtualization.
I compiled packages for VirtualBox and then decided to give KVM a try based on you guys but, I've hit a snag.
My test box is old and does not have BIOS Virtualization. Does anyone have instructions/a link to how to set up QEMU/KVM on boxes without BIOS Virtualization? I was reading through the QEMU wiki and apparently, it will run without the virtualization.
BTW, I'm running 32bit Slack 13 on this machine.
There is nothing special during install. When running, you can use the "-curses" option to let qemu use character terminal (instead of graphics window) as display output.
Distribution: Debian 5 - Slackware 13.1 - Arch - Some others linuxes/*BSDs through KVM and Xen
Posts: 329
Rep:
Quote:
Originally Posted by arfon
I compiled packages for VirtualBox and then decided to give KVM a try based on you guys but, I've hit a snag.
My test box is old and does not have BIOS Virtualization. Does anyone have instructions/a link to how to set up QEMU/KVM on boxes without BIOS Virtualization? I was reading through the QEMU wiki and apparently, it will run without the virtualization.
BTW, I'm running 32bit Slack 13 on this machine.
QEMU can run without virtualization support, but it will run a lot slower. You better try QEMU with KQEMU kernel module.
KVM, on the other hand, *requires* virtualization support (either Intel-VT or AMD-V).
KQemu is still available on slackbuilds.org. I will try to keep it there as long as I can (I'm the maintainer). But it does work with Qemu on 13.0 right now. Not sure yet how it will behave on 13.1.
SOOOooooo, I have to have BIOS Virtualization to get KVM to work?
The short answer is yes. KVM requires BIOS virtulization. KVM will fallback to just QEMU mode if BIOS virtulization is available but the KVM modules are not loaded. QEMU emulation alone is slow without either software acceleration (KQEMU) or hardware (AMD-V or Intel VT) acceleration.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.