Hi Mikkel,
Thanks for the reply. I have written a program today to just do that. But it did not work. As mentioned earlier, my intention was to setup a virtual serial port communication between two windows guests. Forget about connecting the two systems, even the first guest system that boots up, itself is not able to detect the serial port. Tried the following methods: Method 1: socat -x -d -d -d -d -s unix-listen:winsock1,reuseaddr,fork unix-listen:winsock2,reuseaddr,fork both with and without -s option. Result: Unable to detect com port inside windows guest. Method 2: wrote a server program which listens on two UDS sockets and send data to each other. Result: Found that the windows vm is connecting to the server (same in method1 too). The server waits forever in the select call. Unable to detect com port inside windows guest. Method 3: The GUI options to create the socket (one vm as server and the next one as client which does not create) also did not work though I found the file to be created by the vm during bootup. I was still unable to find the serial port inside the windows after doing this. Basically I had rpm installed the latest version of VirtualBox yesterday and opened existing windows VM instances, updated the guest additions & tried the above methods. @Anyone: Please let me know if I am missing some thing here since virtual serial port feature (or documentation?) is something so basic which I do not think is broken. Or may be I am wrong... Regards Sudhakar PS: subject was edited to reflect the new problem. On Mon, Oct 13, 2008 at 10:40 PM, Mikkel L. Ellertson <[EMAIL PROTECTED]> wrote: > Sudhakar L wrote: >> Hi, >> >> Basically I want to debug some vista VM kernel drivers from another >> windows VM using virtual serial cable. >> >> I just want to know if this is possible. Depending on the answer, I >> can save a windows license getting tied to hardware. >> >> >> Regards >> Sudhakar >> > Looking at the documentation, you should be able to connect the com > ports from 2 virtual machines to the same named pipe (windows) or > domain socket (UNIX variants). Just be sure only one VM creates the > socket, and the other uses an existing one, or have both use an > existing one, and create it yourself. If worst cam to worst, you > could create a little program to connect 2 sockets/pipes that > behaves like a null modem cable. I know there are programs that will > connect between a virtual serial port, and a real serial port to let > you monitor the signals. I have used them in the past to monitor > commutations between a Windows program and a UPS. I also built a > primitive software emulation of the UPS... > > Mikkel > -- > > Do not meddle in the affairs of dragons, > for thou art crunchy and taste good with Ketchup! > > _______________________________________________ > vbox-users mailing list > [email protected] > http://vbox.innotek.de/mailman/listinfo/vbox-users > _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
