Conversation

Notices

1. Embed this notice
   Lennart Poettering (pid_eins@mastodon.social)'s status on Friday, 20-Dec-2024 05:05:55 JST Lennart Poettering

   3️⃣7️⃣ Here's the 37th post highlighting key new features of the current v257 release of systemd. #systemd257

   In systemd v256 we added a small tool "systemd-ssh-proxy" whose job is to allow connecting to local VMs with ssh via the AF_VSOCK protocol (as opposed to AF_INET/AF_INET6). It acts as host-side counterpart to the guest-side systemd-ssh-generator that automatically binds sshd to AF_VSOCK.

   In systemd v257 the functionality has been updated so that instead of specifying…

   • Embed this notice
     Lennart Poettering (pid_eins@mastodon.social)'s status on Friday, 20-Dec-2024 05:05:54 JST Lennart Poettering

     in reply to

     This is extremely handy, since it "just works" here. In fact, I switched over to this for my private VM needs entirely now.

     (In related news, systemd-ssh-proxy now supports the AF_VSOCK "MUX" protocol too. This means it's now compatible not only with AF_VSOCK how it's implemented by qemu, but also with the implementations in Firecracker/CloudHypervisor)

   • Embed this notice
     Lennart Poettering (pid_eins@mastodon.social)'s status on Friday, 20-Dec-2024 05:05:54 JST Lennart Poettering

     in reply to

     And that's it! After 37 installments I think I covered pretty much all the bigger things in the NEWS file with a story.

     Of course, there's a lot more in this release. For the full list, consult our NEWS file:

     https://github.com/systemd/systemd/blob/70bae7648f2c18010187c9cf20093155eaa26029/NEWS

     Stay tuned so that you won't miss out on the #systemd258 series when the time comes for the next release!

     James Morris likes this.
   • Embed this notice
     Lennart Poettering (pid_eins@mastodon.social)'s status on Friday, 20-Dec-2024 05:05:55 JST Lennart Poettering

     in reply to

     …the AF_VSOCK "CID" (which is like an IP address, i.e. an identifier for the local VM) you can specify a friendly machine name, if the VM in question is registered with systemd-machined. systemd-vmspawn sets things up that way out of the box, of course. That means, with current off-the-shelf systemd inside a VM and on the host you can now just do "ssh machine/foobar" to connect to a local VM called "foobar", via AF_VSOCK, i.e. independently of any fragile network.