From: Sam Leonard <sam.leonard@codethink.co.uk>
Date: Fri, 19 Apr 2024 15:30:56 +0000 (+0100)
Subject: man: vmspawn - clarify behaviour of omitting --vsock-cid=
X-Git-Tag: v256-rc1~109^2~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9c50fd64b5155fdf0754f1d54ccae75436fdc938;p=thirdparty%2Fsystemd.git

man: vmspawn - clarify behaviour of omitting --vsock-cid=
---

diff --git a/man/systemd-vmspawn.xml b/man/systemd-vmspawn.xml
index ae6a38d49ef..4cf82454f84 100644
--- a/man/systemd-vmspawn.xml
+++ b/man/systemd-vmspawn.xml
@@ -150,12 +150,10 @@
           <term><option>--vsock-cid=<replaceable>CID</replaceable></option></term>
 
           <listitem>
-            <para>Configure vmspawn to use a specific CID for the guest.</para>
-
-            <para>If the option is not specified or an empty argument is supplied the guest will be assigned a random CID.</para>
-
-            <para>Valid CIDs are in the range <constant>3</constant> to <constant>4294967294</constant> (<constant>0xFFFF_FFFE</constant>).
-            CIDs outside of this range are reserved.</para>
+            <para>Sets the specific CID to use for the guest.
+            Valid CIDs are in the range <constant>3</constant> to <constant>4294967294</constant> (<constant>0xFFFF_FFFE</constant>).
+            CIDs outside of this range are reserved. By default vmspawn will attempt to derive a CID for the guest derived from the machine name,
+            falling back to a random CID if this CID is taken.</para>
 
             <xi:include href="version-info.xml" xpointer="v255"/>
           </listitem>