I have both qemu-devel and kqemu-kmod-devel installed (and have tried with just the qemu and kqemu-kmod ports as well). However there is no noticeable difference in speed between qemu with or without the kqemu kernel module loaded. In addition, I can actually unload the kqemu kernel module while qemu is running a guest OS without any impact what-so-ever. I would assume that if qemu was actually using the acceleration provided by kqemu, I would get a message that the module was busy.

I have also noticed that loading the kqemu module does not result in a /dev/kqemu device being created like it does under Linux...

I've always assumed that if the kld was loaded when you started qemu, it'd be taken advantage of. All documentation I've read suggests that this is indeed the case.

That's what I thought, too, but that doesn't appear to be the case. Shouldn't it complain when I try to unload the module while qemu is running? Or wouldn't qemu at least get majorly screwed up if it was actually using the kqemu accelerator? And the lack of a /dev/kqemu device really concerns me, though I have no idea if that is normal or not.

I have both qemu-devel and kqemu-kmod-devel installed (and have tried with just the qemu and kqemu-kmod ports as well). However there is no noticeable difference in speed between qemu with or without the kqemu kernel module loaded. In addition, I can actually unload the kqemu kernel module while qemu is running a guest OS without any impact what-so-ever. I would assume that if qemu was actually using the acceleration provided by kqemu, I would get a message that the module was busy.

If aio and kqemu modules are not loaded then you will get that warning:

Code:

# qemu ...
warning: aio not (kld)loaded, may cause `Invalid system call' traps on disk IO
Could not open '/dev/kqemu' - QEMU acceleration layer not activated: No such file or directory

Quote:

Any thoughts?

Try qemu (without -devel) maybe newest version tries to talk in some different way with kqemu while kqemu version in Ports my be outdated.

__________________religions, worst damnation of mankind"If 386BSD had been available when I started on Linux, Linux would probably never had happened." Linus TorvaldsLinux is not UNIX! Face it! It is not an insult. It is fact: GNU is a recursive acronym for “GNU's Not UNIX”.vermaden's:linksresourcesdeviantartspreadbsd

Sorry, user error. When I first built qemu from ports originally, I saw that it had a kqemu option. I, incorrectly, assumed that this would just build the kqemu kernel module. In fact, qemu has to be compiled to make use of the kernel module. So now it's working :-)

Unfortunately, the difference in speed isn't that great, but it's something at least.

A complete howto for setting up and running qemu on amd64, is one available?

From QEMU Makefile:

Code:

ONLY_FOR_ARCHS= amd64 i386

So nothing changes here, you do all the things as you would do for i386.

__________________religions, worst damnation of mankind"If 386BSD had been available when I started on Linux, Linux would probably never had happened." Linus TorvaldsLinux is not UNIX! Face it! It is not an insult. It is fact: GNU is a recursive acronym for “GNU's Not UNIX”.vermaden's:linksresourcesdeviantartspreadbsd