06 Oct, 2017

1 commit

  • This patch adds the sock_diag interface for querying sockets from
    userspace. Tools like ss(8) and netstat(8) can use this interface to
    list open sockets.

    The userspace ABI is defined in and includes
    netlink request and response structs. The request can query sockets
    based on their sk_state (e.g. listening sockets only) and the response
    contains socket information fields including the local/remote addresses,
    inode number, etc.

    This patch does not dump VMCI pending sockets because I have only tested
    the virtio transport, which does not use pending sockets. Support can
    be added later by extending vsock_diag_dump() if needed by VMCI users.

    Signed-off-by: Stefan Hajnoczi
    Signed-off-by: David S. Miller

    Stefan Hajnoczi
     

29 Aug, 2017

1 commit

  • Hyper-V Sockets (hv_sock) supplies a byte-stream based communication
    mechanism between the host and the guest. It uses VMBus ringbuffer as the
    transportation layer.

    With hv_sock, applications between the host (Windows 10, Windows Server
    2016 or newer) and the guest can talk with each other using the traditional
    socket APIs.

    More info about Hyper-V Sockets is available here:

    "Make your own integration services":
    https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/make-integration-service

    The patch implements the necessary support in Linux guest by introducing a new
    vsock transport for AF_VSOCK.

    Signed-off-by: Dexuan Cui
    Cc: K. Y. Srinivasan
    Cc: Haiyang Zhang
    Cc: Stephen Hemminger
    Cc: Andy King
    Cc: Dmitry Torokhov
    Cc: George Zhang
    Cc: Jorgen Hansen
    Cc: Reilly Grant
    Cc: Asias He
    Cc: Stefan Hajnoczi
    Cc: Vitaly Kuznetsov
    Cc: Cathy Avery
    Cc: Rolf Neugebauer
    Cc: Marcelo Cerri
    Signed-off-by: David S. Miller

    Dexuan Cui
     

02 Aug, 2016

1 commit


14 Oct, 2013

1 commit


11 Feb, 2013

1 commit

  • VM Sockets allows communication between virtual machines and the hypervisor.
    User level applications both in a virtual machine and on the host can use the
    VM Sockets API, which facilitates fast and efficient communication between
    guest virtual machines and their host. A socket address family, designed to be
    compatible with UDP and TCP at the interface level, is provided.

    Today, VM Sockets is used by various VMware Tools components inside the guest
    for zero-config, network-less access to VMware host services. In addition to
    this, VMware's users are using VM Sockets for various applications, where
    network access of the virtual machine is restricted or non-existent. Examples
    of this are VMs communicating with device proxies for proprietary hardware
    running as host applications and automated testing of applications running
    within virtual machines.

    The VMware VM Sockets are similar to other socket types, like Berkeley UNIX
    socket interface. The VM Sockets module supports both connection-oriented
    stream sockets like TCP, and connectionless datagram sockets like UDP. The VM
    Sockets protocol family is defined as "AF_VSOCK" and the socket operations
    split for SOCK_DGRAM and SOCK_STREAM.

    For additional information about the use of VM Sockets, please refer to the
    VM Sockets Programming Guide available at:

    https://www.vmware.com/support/developer/vmci-sdk/

    Signed-off-by: George Zhang
    Signed-off-by: Dmitry Torokhov
    Signed-off-by: Andy king
    Signed-off-by: David S. Miller

    Andy King