Sudhakar L wrote: > 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. > > You are correct - it is not working as documented. Time to file a bug report. Using a virtual serial port should not even need the guest extensions to work. I have started playing with it as well, and while I can connect to the socket created by VB, the VC can not open the COM port associated with the other end.
It is not covered in the documentation, but I would expect that if things were working correctly, that you could create the socket with one VC, and connect to it with a second VC, and it would act like a null modem between the two VC serial ports. 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
