[SOLVED] qemu-kvm No KVM

AndrewSerk · #1 11th March 2011, 06:28 PM

Trying to run a qemu-kvm and it is a no go. The command I am using is:

Code:

 qemu-kvm -m 2000 --cpu core2duo -smp 2,maxcpus=2,cores=2,threads=2,sockets=1  -enable-kvm -cdrom  SL-60-x86_64-2011-03-07-LiveDVD.iso -usbdevice tablet -soundhw ac97 -vga qxl -spice port=$$$$$,password=XXXXXXXXXXXXX

When I try to run it I get:

Code:

open /dev/kvm: No such file or directory
Could not initialize KVM, will disable KVM support

Code:

$$ rpm -q qemu-kvm virt-manager virt-viewer python-virtinst
qemu-kvm-0.14.0-2.fc15.x86_64
virt-manager-0.8.6-2.fc15.noarch
virt-viewer-0.3.1-1.fc15.x86_64
python-virtinst-0.500.5-2.fc15.noarch

Code:

# egrep '(vmx|svm)' --color=always /proc/cpuinfo
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow vnmi flexpriority
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow vnmi flexpriority
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow vnmi flexpriority
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow vnmi flexpriority

Am I missing something here or is it just broke?

Isaac1357 · #2 11th March 2011, 08:56 PM

I'm not running 15 yet, so I can't speak to whether it's working for anyone or not, but have you made sure the kvm kernel modules got loaded?

do an "lsmod |grep kvm" and see what it spits out.

AndrewSerk · #3 11th March 2011, 10:39 PM

Thank you for the post,

I did have to load the kvm kernel modules manually with modprobe, but that doesn't seem to be the only issue. I did a:

Code:

echo "modprobe kvm" >> /etc/rc.local

to see if it would auto load and it did

Code:

# lsmod|grep kvm
kvm                   306680  0

I still get:

Code:

open /dev/kvm: No such file or directory
Could not initialize KVM, will disable KVM support

Thank you again,

Andrew

Isaac1357 · #4 11th March 2011, 10:57 PM

You're still missing one. There's the general KVM module, and then the CPU specific one...

On Intel, you should have "kvm" and "kvm_intel"

On AMD, you should have "kvm" and "kvm_amd"

AndrewSerk · #5 11th March 2011, 11:04 PM

That was it! I forgot about the kvm_intel . Thank you.

..Now a whole set of other issues

:

Code:

qemu-kvm: /builddir/build/BUILD/qemu-kvm-0.14.0/qemu-kvm.c:1724: kvm_mutex_unlock: Assertion `!cpu_single_env' failed.
Aborted (core dumped)

Isaac1357 · #6 11th March 2011, 11:12 PM

LOL Glad I could help a little

The real question is why aren't they automatically getting loaded on boot? Not that it's not painfully easy to work around, of course.

Ahh... no idea on your new problem unfortunately.

Out of curiosity, is it breaking when you create and start a VM from within virt-manager?

AndrewSerk · #7 11th March 2011, 11:55 PM

Quote:

Originally Posted by Isaac1357

Out of curiosity, is it breaking when you create and start a VM from within virt-manager?

You know I haven't tried it through virt-manager or virsh. I hope to have the time to try tonight.

Thanks again for your help,

Andrew

Isaac1357 · #8 11th March 2011, 11:56 PM

No problem

Keep me posted if ya don't mind, I'm curious to see how this works out.

AndrewSerk · #9 12th March 2011, 04:09 AM

Quote:

Originally Posted by Isaac1357

No problem

Keep me posted if ya don't mind, I'm curious to see how this works out.

Sure, It would be my pleasure

---------- Post added at 11:09 PM ---------- Previous post was at 07:01 PM ----------

I am able to get qemu with kvm support when using virt-manager.
I first tried to start it through the gnome shell user interface but virt-manager froze. I ended up running it from the CL as root.

I had previously installed spice-client and spice-server and was pleasantly surprised to find spice-server as a option in virt-manager. I didn't like that it is limited to ports 5900-5999. After getting the proper hardware installed for spice (ac97 sound, vga and qxl video, tablet ) I have a VM with sound, and I can adjust the display size from within the guest.

That's a first for me with virt-manager.

From the spice client I do get a : Warning: no factory for 8 but everything I have tried works.

I will continue this exploratory adventure by looking into/trying boxgrinder next.

ultra magnus · #10 12th March 2011, 07:46 PM

Thanks for this, modprobe kvm and modprobe kvm_amd did it for me.

---------- Post added at 11:46 AM ---------- Previous post was at 11:20 AM ----------

still slow as something, and is pretty unusable compared to the same stuff on f-14 :/

---------- Post added at 11:46 AM ---------- Previous post was at 11:46 AM ----------

still slow as something, and is pretty unusable compared to the same stuff on f-14 :/

AndrewSerk · #11 13th March 2011, 04:04 AM

Quote:

Originally Posted by ultra magnus

Thanks for this, modprobe kvm and modprobe kvm_amd did it for me.

still slow as something, and is pretty unusable compared to the same stuff on f-14 :/

My pleasure,Glad you where able to get things working.

I haven't seen any slowing here and everything I have tried for VM through virt-manager works well. Not sure what might be causing slow operations for you.

I have just been running custom livecd spins through virt-manager with spice and haven't tried to do a install yet.

ultra magnus · #12 13th March 2011, 06:07 AM

This is the command I use:

Code:

qemu-kvm -drive file=/var/lib/libvirt/images/WindowsServer2003.img,if=virtio,boot=on -usbdevice tablet -soundhw ac97 -net nic,model=virtio -net tap -vga qxl -spice port=5931,disable-ticketing -enable-kvm -m 256M

That works in F-14 and I get really good performance, with my win 7 vm I can watch 720p on youtube without problems, but now it takes ages to even boot. And I seem to be missing all virtio devices in virt-manager. Unless something has changed regarding those?

AndrewSerk · #13 13th March 2011, 06:48 AM

I had problems also when calling qemu-kvm from the CL, so I switched to virt-manager. You might want to give virt-manager a try as it has worked pretty well here for me. It just might be worth a try.

---------- Post added at 01:29 AM ---------- Previous post was at 01:11 AM ----------

I noticed that with some VM's vmvga works better than vga with qxl. All the virtio devices I have tried here have worked. I even mounted a usb flash drive in a VM all through virt-manager. Who would think a GUI would work better than CLI.

---------- Post added at 01:48 AM ---------- Previous post was at 01:29 AM ----------

Yup, I was just testing some things from the command line and for me a simple qemu-kvm works from the CL Something like

Code:

qemu-kvm -m 1000 -cdrom F14.iso -enable-kvm

but if I put spice and other in like:

Code:

qemu-kvm -m 2000 --cpu core2duo -smp 2,maxcpus=2,cores=2,threads=2,sockets=1  -enable-kvm -cdrom  SL-60-x86_64-2011-03-07-LiveDVD.iso -usbdevice tablet -soundhw ac97 -vga qxl -spice port=$$$$$,password=XXXXXXXXXXXXX

It crashes and I get:

Code:

qemu-kvm: /builddir/build/BUILD/qemu-kvm-0.14.0/qemu-kvm.c:1724: kvm_mutex_unlock: Assertion `!cpu_single_env' failed.
Aborted (core dumped)

I also noticed that -vmvga is only available in virt-manager.

ultra magnus · #14 13th March 2011, 06:59 AM

I see that error too, alpha is unstable software?? oh noes

AndrewSerk · #15 13th March 2011, 07:03 AM

Quote:

Originally Posted by ultra magnus

I see that error too, alpha is unstable software?? oh noes

Who would of thunk it.

I am surprised that the things that fail from CLI, work in the GUI .