Bug: Socket-to-Serial Communications

[ewiley]

I am trying to communicate between VMs and ESX 3.5 using emulated serial lines. The destination on the ESX machine is a socket and the source is an application writing directly to COM2. The communication is unreliable even though the transfer is all done on one physical machine. Data disappears during socket-to-serial communications between Win32 and ESX during ESX to VM communications. As speed increases, loss is more likely. I have tried various settings and transfer speeds, and believe the cause to be a bug in ESX.

[AndreTheGiant]

What do you mean with socket.

The serial inside a VM coul be only:

• a physical serial port (it become exclusive, so is not your case)

• a file

• a named pipe

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

[ewiley]

Inside the VM I'm interacting with COM2. On the ESX I'm interacting with a socket.

[RParker]

Inside the VM I'm interacting with COM2. On the ESX I'm interacting with a socket.

Supposedly ESX 4.0 has better interoperability with Serial / USB ports. Have you tried ESX 4.0? If it's what you are using now, then I'd say it was a bug, but calling VM Ware and starting an SR may be the only viable option.