> arch=qemu, arch=vmware anyone? Unlike with xen, it should not be necessary to create a different arch to run things in qemu. I was impressed that it can happily run the 9 different operating systems I tried with it, with very few problems.
I guess it's difficult to know whether the bug is in openbsd or qemu or both. IIRC some qemu people said it's to do with some difference in handling / using interrupts which may be tickling a bug in qemu. I think to fix it properly might need someone who is an expert qemu developer qemu to work together with someone who is an expert with the kernel in openbsd (or netbsd as the bug occurs there also). I think this would be worthwhile, but as I am expert in neither, I can't really help much with this except to encourage it. qemu does claim *bsd guest compatibility so it would be good if a qemu developer would take the initiative in organizing to fix these things. The existance of a hackaround as I have described (disabling mpbios, acpi, smp) means people can run openbsd and netbsd with networking in current qemu under Linux or another host OS. This can be good for people like me who don't currently use bsd as their main OS, but want to test software on it or try it out. Sam
