Hello, Some people have reported having troubles with kqemu. Actually, they are not having problems with user kqemu, but kernel kqemu. With just modprobe kqemu and no -kernel-kqemu, one gets kqemu acceleration in guest's user mode and that works plain fine. -kernel-kqemu enables acceleration for the guest's kernel, but as explained in the technical documentation, that can not work for all guest systems, because kqemu has limitations. I've identified the problem that Mach has, see the my qemu-devel mailing list post. I've put a fixed gnumach on
http://dept-info.labri.fr/~thibault/tmp/gnumach if people want to give it a try. Yes, the EATA probing loop takes some time. This is because with -kernel-kqemu, the udelay calibration loop gets completely wrong and thus udelay() loops much more than needed. That being said, people may want to perform real tests, but I doubt -kernel-kqemu will provide a lot of speedup compared to juste modprobe kqemu: GNU/Hurd spends most of its time in userland in servers ;) Samuel
