FYI, works with or without "--enable-kvm" here

Attached Thumbnails

 

For me it doesn't.
I only get the first line (BIOS notification) in the first screen.
(Not shown in the picture.)
After that nothing, but the guest is not aborted either. The VM seems to be running still.

My "raw" qemu run:

https://www.dropbox.com/s/a9t3q49y57mn67y/qemu.png

And the aqemu whining:

Disabled kvm:
https://www.dropbox.com/s/tm3vdxnmyi2w160/aqemu_kvm.png

and the pop-up:
https://www.dropbox.com/s/77ykc0xsng...qemu_whine.png
Ignoring the error leaves an empty qemu-window.

Turboscrew, I have the same problem, or a related one.

The VM shows nothing, or has a frozen graphic; however if one runs it with -nographic, one can connect to the VM via VNC or ssh (assuming it has been set up).

I don't think it's kvm related, as my processor does all that just fine.

It seems to be a graphics issue, because if I passthrough one of my video cards, it works perfectly. There's something odd about the latest slackware 64/ qemu 2.0 SBo build, but I haven't figured it out yet.

Phooh, I'm not alone...

Maybe you guys could try adding
-vga std
to your qemu command. See if it helps

Actually the gtk interface, gave me so much trouble,
that I disabled it with the configure "--disable-gtk"

so try using sdl, it may work!

Enjoy

the gtk interface didn't work in the past (frozen screen, happened just before 14.1) because of cairo but this now has been fixed (in -current and in /patches for 14.1) so it should work fine (the sdl one is deprecated and will be removed in the future).

1 members found this post helpful.

I've tried -vga std, and just about every other option. I can tell you this: if I use virt-manager, as opposed to the command line qemu, then I get "cannot connect to console". I also get a message about USB redir, which is odd because I compiled it with usbredir, but that is probably unrelated. I'll look in /patches to see if something didn't get applied, but not sure how that'd have happened.

I think you probably need to replace the nc shipped with Slackware with netcat-openbsd, as indicated in libvirt's README.

Nope.
Although I didn't expect it would - it did print: the bios-message.

Oops - I was wrong. It is about output:
I edited the Makefile: copied the ELF to vmox.sym before stripping takes place.

Term 1:
Term 2:
from "nm vmox.sym":
00115998 T main
00116bc3 T ox_main

The running advances, but only the seabios text is shown.
The prink-outputs don't come through.

Aqemu checks for loaded kvm modules by default. Aqemu hasn't been updated in ages. Don't use it. Newer qemu, since the kvm merge, has introduced a lot of command line changes. The qemu changelogs list the breakages/changees from previous versions.

Note that "qemu-kvm" is a symlink to "qemu-system-x86_64" in the SBo install. Also, if you use qemu-system-*, I think you need the correct kvm module loaded even if its not used.

Depending on how the iumage was created (hardware, PAE, CPU, memory, etc), you may have to include those in the command line if qemu can't autodetect. Besides -cpu you may need to specify -machine. Look at "man qemu" for all the goodies as well as information on the qemu console.

Edit: Oops, didn't read the second page of posts. Since ponce was able to create an image that ran, (1) the OP image is incorrect, (2) the OP qemu install is incorrect.

I very much suspect the latter. See my debugging results: Debugging works, but the printk-text doesn't end up onto the display.

if you want to test the image I built, it's here.