From: Laurence Kiln <246209442+LaurenceKiln@users.noreply.github.com>
Date: Thu, 27 Nov 2025 11:17:57 +0000 (+0200)
Subject: DOC: update Ssh= to note sd-v256+ already generates sshd-vsock
X-Git-Tag: v26~51
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=df53510982b25517455b5f55794e1317e14e5f8d;p=thirdparty%2Fmkosi.git

DOC: update Ssh= to note sd-v256+ already generates sshd-vsock
---

diff --git a/mkosi/resources/man/mkosi.1.md b/mkosi/resources/man/mkosi.1.md
index b64780a76..51ceac2e7 100644
--- a/mkosi/resources/man/mkosi.1.md
+++ b/mkosi/resources/man/mkosi.1.md
@@ -1243,6 +1243,12 @@ boolean argument: either `1`, `yes`, or `true` to enable, or `0`, `no`,
     enable SSH access to any virtual machines via `mkosi ssh`. To access
     images booted using `mkosi boot`, use **machinectl**.
 
+    Starting with systemd v256, systemd-ssh-generator(8) will automatically
+    provide `sshd` over VSock when running inside a VM. So if you're using a
+    recent version of systemd inside a VM, this option is generally not used.
+    You still need openssh installed in the image, and the default setting of
+    `--vsock=auto` is enough to ensure a VSock is available inside the VM.
+
 `SELinuxRelabel=`, `--selinux-relabel=`
 :   Specifies whether to relabel files to match the image's SELinux
     policy. Takes a boolean value or `auto`. Defaults to `auto`. If