win10 + hyperv + multipass + ubuntu

Can someone provide the correct parameters to start 'gvproxy-windows.exe' on windows and and './vm' in linux hyperrv vm?

I'm not sure gvproxy-windows.exe works together with vm, I've never used both :-/ You need to configure your hyperv VM to use hvsock, see the first answer to https://stackoverflow.com/questions/60696166/using-the-hyper-v-sockets-between-windows-host-and-linux-guest

Can you provide all the steps you did to set this up. Eg, did you set the registry setting?

@cfergeau What I wolud like to do is the same done by wsl-vpnkit https://github.com/sakai135/wsl-vpnkit but on a plain hyperv vm (without WSL)

I suppose gvproxy-windows.exe works together with vm look at https://github.com/sakai135/wsl-vpnkit/blob/main/distro/alpine.dockerfile

@gbraad I confirm, I set up the registry as described here https://github.com/containers/gvisor-tap-vsock#windows-prerequisites but no connection happen

I would first debug this using an intermediate tool either on the host (https://stackoverflow.com/questions/60696166/using-the-hyper-v-sockets-between-windows-host-and-linux-guest mentions hvc) or on the guest (netcat or socat) to make sure a connection can be established to the other end. Once you are able to create the vsock/hvsock connection, then you can try to get gvproxy/vm to communicate.

Ok I did a test:

• on windows use hvc nc -t vsock hyperv-ubuntu-lts 1234 to listen on 1234
• on linux connect to ncat -l --vsock 1234
• I can exchange chars in both directions

Then you can start vm in the VM, and see if it can connect to the host?

I am able to verify windows hyperv setup, it is working the windows registry in Readme the Rock/blob/main/README.md?plain=1#L69) is critical and it is using port 1024, if you changed to other ports, you need update GUID accordingly

# 1024 hex code is 400, the first part of GUID
$service = New-Item -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\GuestCommunicationServices" -Name "00000400-FACB-11E6-BD58-64006A7986D3"
$service.SetValue("ElementName", "gvisor-tap-vsock")

gvproxy-windows.exe -debug -listen "vsock://00000400-FACB-11E6-BD58-64006A7986D3"

On linux

# make sure to restart linux vm after adding registry if they are started alreday
sudo modprobe hv_sock
gvforwarder -stop-if-exist none -url vsock://2:1024/connect #change 1024 to match port in guid
# view forwarded ports
curl http://192.168.127.1/services/forwarder/all
# add port forwarding
curl http://192.168.127.1/services/forwarder/expose -X POST -d'{"local":"127.0.0.2:9022", "remote":":22"}'

On windows

ssh 127.0.0.2 -p 9022