I am just talking off the top of my head but doesn't Plan9 Support Posix?If it does then I would think the next step would be to port SDL to Plan9 since I know that Qemu for Linux uses SDL for audio and video support.
You other option would be to rewrite QEMU to use the native graphics and audio
Alexey Eremenko wrote:
For example the documentation is very poor about running Qemu under
Windows host, with it's lacking details about Windows networks.
Maybe you like to check if QEMU Wiki
http://kidsquid.com/cgi-bin/moin.cgi/QemuOnWindows
can help you (and link at bottom of that page).
See also:
http://www.h7.dion.ne.jp/~qemu-win/ (Documentation section below)
Thank you very much.
I have found something useful: TAP for Windows - that is - virtual
ethernet network driver for Win NT based systems.
So basically only those docs were relevant:
But unfortunately, it comes separately from Qemu package, inside
OpenVPN software.
So my recommendation is to:
1) get the TAP driver out of OpenVPN package, and
2) put it into Qemu setup, and
3) update user docs with that.
I dunno if I will succeed in getting the driver out of OpenVPN, it
TLS and multithreaded applications are known to not work with usermode
emulation.
We use python for compiling python modules inside scratchbox. So I
need to fix this or find a workaround (undef Py_HAVE_NATIVE_TLS?).
What must be done for implementing TLS + multithread in qemu? Maybe I can
What must be done for implementing TLS + multithread in qemu? Maybe I can
help.
* Implement the TLS syscalls (futexes and the architecture specific bits).
There's a patch for clone() here: https://nowt.dyndns.org/patch.qemu_nptl
* Fix all the bits of qemu that aren't threadsafe (mainly the TB
On Monday 18 September 2006 21:05, Rafael Espíndola wrote:
Running python 2.4 in qemu sometimes causes this assert
Inconsistency detected by ld.so: rtld.c: 288: _dl_start_final:
Assertion `info-l.l_tls_modid == 0' failed!
TLS and multithreaded applications are known to not work with usermode
