VMware {code} Community
voodooRod
Contributor
Contributor

VMCI Again

Early last year I looked into VMCI and found it wasn't what I needed to communicate with VMs. So, I rolled my own stream socket communication and all worked well. Upgrading to VMWorkstation 6.0, then caused me to see my sockets being dropped by the VM after running for some time. Keep Alives didn't help. So, now upgrading to 6.5 I'm returning to VMCI to see if it will keep the connection up and running.

Last time I looked at VMCI there was a datagram api. Am I correct in my understanding that, it has been depracated, and I must roll my own VMCI/Winsock sockets?

Also, before I make this leap, does anyone know why TCP stream sockets inside the VM would be dropped after running a while. They work, but after about 30 minutes the connection is dropped.

thanks,

Rod

0 Kudos
1 Reply
njain
Expert
Expert

With VMCI Sockets 1.0 release, the datagram API and shared memory API have been deprecated. You will now need to implement your own VMCI sockets.

0 Kudos