In commit 5379392731b52eef22b4936637eb592b93e04318, the following change was introduced:
modified gnu/system/vm.scm @@ -941,6 +941,7 @@ with '-virtfs' options for the host file systems listed in SHARED-FS." '()) "-no-reboot" + "-nic" "user,model=virtio-net-pci" "-object" "rng-random,filename=/dev/urandom,id=guixsd-vm-rng" "-device" "virtio-rng-pci,rng=guixsd-vm-rng" Unfortunately, this means that in our docs where we suggest doing the following: `guix system vm config.scm` -nic user,model=virtio-net-pci,hostfwd=tcp::10022-:22 Since we now provide our own similar "-nic" field this creates a *second* network interface at the same address and there is a race as in terms of which handles connections. Depending on the race result, connections to the forwarded port may hang indefinitely. Ironically, this regression was introduced to solve another regression! >From the commit message: This fixes a regression introduced in 8e53fe2b91d2776bc1529e7b34967c8f1d9edc32 where 'guix system vm' would no longer be using virtio. What's the right solution? One could be that "guix system vm" itself could take an argument that sets up port forwarding in the generated shell script. Eg: guix system vm config.scm --hostfwd=tcp::10022-:22 --hostfwd=tcp::8888-:80 kind of ugly, but it could work. WDYT? - Chris