This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Cathy Avery
Recipients Cathy Avery, gregory.p.smith, kushal.das, r.david.murray
Date 2016-12-19.13:09:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
First make sure the driver is in your kernel. It will be with RHEL. Look in /lib/modeles/"your kernel name"/kernel/net/vmw_vsock/vmw_vsock_vmci_transport. I have never tried it on vmware fusion. I have tested it on ESX. See if there is a VMCI option to enable on your VM's settings. Start the vm and do an lsmod to see if vmw_vsock_vmci_transport is loaded.

I've attached a little C program thats netcat for vsock. Its a quick confirmation that your transport is loaded correctly. It will show you your CID.

run ./nc-vsock

CID = 973033371
CID = 0x39ff4f9b
usage: ./nc-vsock [-l <port> [-t <dst> <dstport>] | <cid> <port>]
Date User Action Args
2016-12-19 13:09:07Cathy Averysetrecipients: + Cathy Avery, gregory.p.smith, r.david.murray, kushal.das
2016-12-19 13:09:07Cathy Averysetmessageid: <>
2016-12-19 13:09:07Cathy Averylinkissue27584 messages
2016-12-19 13:09:06Cathy Averycreate