Hi, It is an experimental serial port support for win32. Here is patches and a binary. http://www.h7.dion.ne.jp/~qemu-win/download/qemu-20060311-serial-3.patch http://www.h7.dion.ne.jp/~qemu-win/download/qemu-20060311-16550a.patch http://www.h7.dion.ne.jp/~qemu-win/download/qemu-20060311-serial-win2kxp.patch
http://www.h6.dion.ne.jp/~kazuw/qemu-win/qemu-20060311-serial.zip The 16550A patch is by Benoit Canet from here. http://lists.gnu.org/archive/html/qemu-devel/2006-02/msg00004.html An option is: -serial COM1 Use upper-case for COM number. Dialog is popped up and set communication parameters. After patches are applied and the first time Windows boots, Windows recognizes the device is updated. So wait until a device driver is installed and reboot. I have not tested a real COM port. I used ComEmulDrv which provides a virtual COM port pair as a device driver for Win2k/XP. I set COM5 and COM6 by it and used HyperTerminal on both Win2k guest and WinXP host. Files can be transfer between them. http://mixw.net/related.htm#tncemu Communication parameters are important. Tested parameters are: Baud rate: 9600 bps Data bit: 8 bit Parity: none Stop bit: 1 Flow control: none It is necessary to set the same parameters among the guest and the host and QEMU. When flow control is hardware, if qemu-20060311-serial-win2kxp.patch is not used, data can not be sent from Win2k guest to WinXP host. It is too slow to use windbg. I will try to make a patch to use a named pipe for it. Regards, Kazu _______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
