Tried it with the same problems I've been having earlier.

Also, if kvm-intel is needed (to be loaded, not used - I can get loaded without kvm ;-) ), that's it then:
It doesn't even load if the HW doesn't have virtualization support.
(like my Pentium M,)

If output of is empty you can't use kvm. The vmx flag is needed for kvm-intel as stated here. So if you don't have it it's pretty normal that modprobe kvm-intel fails

Pentium M doesn't have those. It doesn't support HW acceleration of virtualization.

I checked that the printk-stuff is written in video memory (0xB8000 = CGA?) of the VM and I guess it should show up as output to console in the qemu-window, but it doesn't.
I understand tha vga should be in 0xA0000?

Any idea why not, how to fix the problem?
Could it be that libvirt is needed for it to work? And thus kvm and HW support?

The http://qemu-buch.de doesn't seem to be usable anymore, and there seems to be no
discussion forums for qemu where I could ask.

Anyway this looks like a problem that is not related to any distros in any way.
I guess no compilation flags could solve the problem.

Try the mailing list here. All mailing lists are listed there. Not all projects run fora.

Thanks, I will.
No, I know. Fora are just "nicer".
I once put myself in a kernel mailing list. 98% of the mail was spam. And the spamming doesn't, of course, end if you drop off from the mailing list. Tha spam still keeps coming.
So you better get a specific mailbox for that.

If you don't have support in your CPU for the kvm modules then maybe you could try the older qemu-legacy + the kqemu kernel module. They are no longer part of slackbuilds.org since 14.1 so you'll need to use older versions, but the code hasn't changed:

http://slackbuilds.org/repository/14...m/qemu-legacy/
http://slackbuilds.org/repository/13.37/system/kqemu/

You'll need to uninstall your current qemu package to get it working. Before starting qemu do a 'modprobe kqemu'. This will only work for x86 systems.

Hope this helps

@ponce: I tried your vmox.img; seems like it works fine, clearly I had a different qemu problem. I figured it out: when I recompiled the kernel, somehow I left CONFIG_DRM_CIRRUS_QEMU=n instead of m. So qemu the command line works, but not the virt-manager

Now I have to try that updated nc thing to see if I can get rid of the

that I see in virt-manager. The thing is, I have usbredir, which I built from usbredir.SlackBuild,

but I see the qemu-SlackBuild wants
"libusbredirhost" which usbredir did not apparently build. Where the heck does that come from? From that alternate nc? Or is this a different issue?

if you installed usbredir you should have a /usr/lib${LIBDIRSUFFIX}/pkgconfig/libusbredirhost.pc file (that is checked for).

Hmm, rebuilt qemu-2.0.0, libvirt-1.2.5, libvirt-glib-0.1.8, rebuilt usbredir-0.6, rebuilt virt-manager-1.2.5 and still have the USB redirection error message as well as the no graphical console connection message from virt-manager. qemu works. Grrr, at this point I'm not sure where to begin.

[EDIT] rebuilt the whole virt-manager with sbopkg with the following queue:
But now virt-manager fails with:

Clearly something is wrong with python, but what?

Looks like the gi modules were built, but there is something wrong with the path. Googling around I saw reference to an environment variable $PYTHONPATH, but I don't seem to have one, not that I ever checked before. I'm assuming that this has something to do with the presence of python3. Anyone know anything about this, or should I start a new thread on this problem and come back to the qemu/virt-manager later?

try removing python3 and then rebuilding the queue (you can reinstall it after).
also regarding the queue, you should also build qemu just before libvirt.

2 members found this post helpful.

OK, did that, it all seems to be working properly, thanks!

Rather old post, but the only one that fits the bill with the issue I'm having. What was the fix for the spice video and usb error und virt-manager, I have the exact issue. I also cant use the VNC internal to virt-manager as the video freezes, however if I connect via UltraVNC will work fine. I loved to figure out the Spice issue as it driving me nuts, I'm move from vmware workstation to kvm and I'd really rather not have anything lingering that makes my question it stability to rely on in production. Thanks guys. Btw, I did recompile all the packages in order as mentioned above and qemu was compiled before libvirt, but no help.

Ok, I've seem to work out 90 of the issue, was GTK+2 and GTK+3 issues for me, when building spice-gtk, gtk-vnc, and finally virt-manager it's self. Some how it was mixing GTK+2 and GTK+3 in the code, via running a virt-manager --debug I seen; Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported So I removed GTK+2 and compiled all the way up to the point where it started complaining about GTK+2 missing and added GTK+2 and continued, this fixed the above error and got all the graphical consoles working (spice 99%, vnc 100%). In spice however the keyboard will not work, now via the virt-manager --debug method I see; "(virt-manager:8219): GSpice-CRITICAL **: send_key: assertion `scancode != 0' failed" every time I press a key using spice protocol and the VM see's nothing. Still looks to be a spice issue, but I'm still pounding on it... Any help would be great, thanks guys.