| 6 Mar 2025 |
 gdamjan | raitobezarius: note 258 will have one more vsock implementation vsock-mux/
https://github.com/systemd/systemd/pull/32941 | 19:58:12 |
| gdamjan | or was that in 257? :D | 19:59:03 |
 @elvishjerricco:matrix.org | ok a lot more stuff is making a lot more sense | 19:59:07 |
| @elvishjerricco:matrix.org | still need to look at the ssh generator pr | 19:59:27 |
| gdamjan | yes, one per connection | 20:00:00 |
| gdamjan | (in classic inetd mode, so to speak) | 20:00:09 |
| @elvishjerricco:matrix.org | thanks | 20:00:21 |
| @elvishjerricco:matrix.org | I have a lot to learn about vsock I think | 20:00:29 |
| gdamjan | man 7 vsock :D | 20:00:42 |
| gdamjan | ugh, I remember it, the man page, was longer | 20:01:13 |
| @elvishjerricco:matrix.org | "No manual entry for vsock in section 7" I'm sure it's out there :P | 20:01:13 |
| gdamjan | raitobezarius: I think you DO need the vscok module for the AF_VSOCK | 20:02:04 |
| gdamjan | * raitobezarius: I think you DO need the vsock module for the AF_VSOCK | 20:02:17 |
| @elvishjerricco:matrix.org | this is a tangent but I'm interested in what you mean | 20:03:00 |
| @elvishjerricco:matrix.org | I quite like generators | 20:03:12 |
| gdamjan | but python -c 'import socket;socket.socket(socket.AF_VSOCK, socket.SOCK_STREAM, 0)' did load the modules automatically | 20:03:26 |
| @elvishjerricco:matrix.org | specifically because they don't need nixos | 20:03:26 |
| gdamjan | right, and they take the "live" environment into consideration | 20:04:08 |
| gdamjan | so if I move the same nixos image from bare metal to a vm vsock will start working | 20:04:49 |
| @elvishjerricco:matrix.org | yea it's "discoverable" in a way | 20:05:35 |
| @elvishjerricco:matrix.org | I just had a nice conversation with Kent Overstreet about systemd generators | 20:07:27 |
 raitobezarius | In reply to @gdamjan:spodeli.org
raitobezarius: note 258 will have one more vsock implementation vsock-mux/
https://github.com/systemd/systemd/pull/32941 oh gosh i needed that so hard | 20:07:38 |
| raitobezarius | i just fixed it in my thing | 20:07:45 |
| @elvishjerricco:matrix.org | which is unusual. He's normally quite difficuult | 20:08:04 |
 Arian | ThingOS | 20:08:04 |
| @elvishjerricco:matrix.org | * which is unusual. He's normally quite difficult | 20:08:09 |
| raitobezarius | gdamjan i decided to stop to rely on my shitty memory and fact checked the kernel | 20:08:35 |
| raitobezarius | you're right that vsock is a driver in vhost/ | 20:08:39 |
| raitobezarius | config VHOST_VSOCK
tristate "vhost virtio-vsock driver"
depends on VSOCKETS && EVENTFD
select VHOST
select VIRTIO_VSOCKETS_COMMON
default n
help
This kernel module can be loaded in the host kernel to provide AF_VSOCK
sockets for communicating with guests. The guests must have the
virtio_transport.ko driver loaded to use the virtio-vsock device.
To compile this driver as a module, choose M here: the module will be called
vhost_vsock.
| 20:09:19 |
| raitobezarius | vsock is a either a kernel driver or baked into the kernel | 20:09:27 |
