Linux-man Archive on
 help / color / Atom feed
From: Stefano Garzarella <>
Cc: Jorgen Hansen <>,, Stefan Hajnoczi <>,
	Dexuan Cui <>,
Subject: [PATCH v2] vsock.7: add VMADDR_CID_LOCAL description
Date: Fri, 14 Feb 2020 14:07:49 +0100
Message-ID: <> (raw)

Linux 5.6 added the new well-known VMADDR_CID_LOCAL for
local communication.

This patch explains how to use it and remove the legacy
VMADDR_CID_RESERVED no longer available.

Signed-off-by: Stefano Garzarella <>
    * rephrased "Local communication" description [Stefan]
    * added a mention of previous versions that supported
      loopback only in the guest [Stefan]
 man7/vsock.7 | 19 +++++++++++++++++--
 1 file changed, 17 insertions(+), 2 deletions(-)

diff --git a/man7/vsock.7 b/man7/vsock.7
index c5ffcf07d..78ac22b1e 100644
--- a/man7/vsock.7
+++ b/man7/vsock.7
@@ -127,8 +127,8 @@ There are several special addresses:
 means any address for binding;
 (0) is reserved for services built into the hypervisor;
-(1) must not be used;
+(1) is the well-known address for local communication (loopback);
 is the well-known address of the host.
@@ -164,6 +164,16 @@ Consider using
 when binding instead of getting the local CID with
+.SS Local communication
+(1) directs packets to the same host that generated them. This is useful
+for testing applications on a single host and for debugging.
+The local CID obtained with
+can be used for the same purpose, but it is preferable to use
@@ -222,6 +232,11 @@ are valid.
 Support for VMware (VMCI) has been available since Linux 3.9.
 KVM (virtio) is supported since Linux 4.8.
 Hyper-V is supported since Linux 4.14.
+VMADDR_CID_LOCAL is supported since Linux 5.6.
+Local communication in the guest and on the host is available since Linux 5.6.
+Previous versions partially supported it only in the guest and only with some
+transports (VMCI and virtio).
 .BR bind (2),
 .BR connect (2),

             reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 13:07 Stefano Garzarella [this message]
2020-02-14 19:35 ` Stefan Hajnoczi
2020-02-17 13:55 ` Jorgen Hansen
2020-02-17 17:27   ` Stefano Garzarella

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-man Archive on

Archives are clonable:
	git clone --mirror linux-man/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-man linux-man/ \
	public-inbox-index linux-man

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone