Maximilian Bosch a9adfc631a nixos/test-driver: allow assigning other vsock number ranges ... I'm a little annoyed at myself that I only realized this _after_ #392030 got merged. But I realized that if something else is using AF_VSOCK or you simply have another interactive test running (e.g. by another user on a larger builder), starting up VMs in the driver fails with qemu-system-x86_64: -device vhost-vsock-pci,guest-cid=3: vhost-vsock: unable to set guest cid: Address already in use Multi-user setups are broken anyways because you usually don't have permissions to remove the VM state from another user and thus starting the driver fails with PermissionError: [Errno 13] Permission denied: PosixPath('/tmp/vm-state-machine') but this is something you can work around at least. I was considering to generate random offsets, but that's not feasible given we need to know the numbers at eval time to inject them into the QEMU args. Also, while we could do this via the test-driver, we should also probe if the vsock numbers are unused making the code even more complex for a use-case I consider rather uncommon. Hence the solution is to do sshBackdoor.vsockOffset = 23542; when encountering conflicts.		2025-05-09 11:54:00 +02:00
..
src	nixos/test-driver: allow assigning other vsock number ranges	2025-05-09 11:54:00 +02:00
default.nix	nixos/test-driver: use ipython via ptpython	2025-03-21 12:34:59 +00:00
nixos-test-driver-docstrings.nix
shell.nix