Building SlackBuilds KVM doesn't work, 2.6.35.4 kernel
Hi,
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: Quote:
What now? Thanks |
|
I am using Slackware 13.1 and I'm using this Slackbuild.
I thought qemu-kvm might be some fork or whatever because I read kvm is already a fork of qemu. Then I'll try qemu-kvm. Thanks.^^ |
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**** :D ) 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).
|
Thank you, I got it now.
Quote:
|
Quote:
Code:
modprobe kvm-intel |
Yep, I loaded the kvm-amd module. lsmod verified it.
About the BIOS update: I'd never update a BIOS if it's not absolutely necessary. If it doesn't work due to my BIOS version I'd rather take another virtualization program. |
Quote:
Also, unless i missed something, if you have the hardware virtualization extension enabled you should see a svm (for AMD) or vmx (for Intel) on your /proc/cpuinfo in the flags line. As for qemu, you can alternate to the VM console using ctrl+alt+2 and run "info kvm" to see if it go the kvm support enabled. |
Like I said, you only need to worry about the CPU or BIOS if the modules didn't load. You're good to go.
So is the slowness you're experiencing related to anything in particular (e.g. display, drives, network)? How are you starting the vm? What command? |
These are my flags:
Quote:
Like I said, you only need to worry about the CPU or BIOS if the modules didn't load. You're good to go. Quote:
Quote:
Code:
$ qemu -m 2047 -hda ./Qemu/slackware13.1.img -cdrom ./Downloads/slackware-13.1-install-dvd.iso -boot d |
Quote:
EDIT: Disregard... You must have been typing when I asked this question. |
Just "qemu".
|
Quote:
The qemu command is just the emulator without any acceleration. It's slower than qemu-kvm even if you add the -enable-kvm option. Use qemu-system-x86_64 in place of qemu. Don't worry about the reference to x86_64 if you're running 32 bit because it works for both 32 bit and 64 bit. If I've kept up so far, you've installed packages for qemu, kvm and qemu-kvm. As mentioned earlier in the thread, all you need is qemu-kvm. I suggest you uninstall the qemu and kvm packages. |
Ah, this explains a lot. I read about qemu-system-x86_64 but I didnt used it because I didnt want 64bit.^^
I'll try then. Thannks! |
I didn't know there was a difference between qemu and qemu-system-x86_64 - i use "qemu" for i[456]86 machines and the performance seems the same. :\
Anyway, my performance bottleneck usually is the weird disk caching of qemu, so i just disable it and everything runs smooth again. Basically, i use: Code:
-drive index=0,media="disk",if="virtio",cache="none",file="/home/max/vms/disks/slack64-build.img",boot="on" Code:
-hda /home/max/vms/disks/slack64-build.img |
All times are GMT -5. The time now is 03:03 AM. |