[SOLVED] Building SlackBuilds KVM doesn't work, 220.127.116.11 kernel
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.
Building SlackBuilds KVM doesn't work, 18.104.22.168 kernel
since there was a lot of talk about virtualization I thought I try kvm -- before I used VirtualBox.
I took the SlackBuild from SlackBuilds.org and got an error with u8 as type in /usr/include/scsi/scsi.h. (sorry, I don't have the exact error message anymore..) I searched for its definition and I only found __u8 in /usr/include/linux/types.h. Then I searched the web and found a "fix" which says I have to change u8 from /usr/include/scsi/scsi.h to __u8.
Okay, this problem was solved, but when I run the SlackBuild now it stops at some point and I don't know why. These are the last few lines of output:
I put an echo after the make for building kvm and I put an echo after "make install". None of them are printed.
as you can see here, kvm is the name of the old version of the package stopped in 2009, userspace tools (the modified qemu) and the kernel modules: with 2010 (someone correct me if I'm saying bull**** ) they are packaging only the new stable branch named qemu-kvm containing only the userspace tools (as the kvm modules are already shipped with your distribution's kernel).
But it is still very slow. I think I'll read some tutorials about kvm and if it won't be faster I'll change back to VirtualBox or VMware.
Did you load the kvm modules first:
- or -
If either of those don't load then either your CPU doesn't support virtualization or your motherboard BIOS doesn't support virtualization. A BIOS upgrade is sometimes needed to gain access to the virtualization of the motherboad depending on how old it is.