search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.26k stars 812 forks source link

Hyper-V Socket HV_GUID_WILDCARD not working for WSL2 vms #5751

Closed jpathy closed 7 months ago

jpathy commented 4 years ago

Environment

Windows build number: [10.0.20185.0]
Your Distribution version: [20.04]
Whether the issue is on WSL 2 and/or WSL 1: [WSL 2]

Steps to reproduce

If you run a AF_HYPERV server with HV_GUID_WILDCARD / HV_GUID_CHILDREN as VmId, the vsock client inside the vm can't connect to it. Only running on the actual VmId of the VM (obtained from hscdiag, this requires admin priviledge) works. Is there anyway to serve multiple wsl2 vms without needing admin access and listening on all VmIds?

Expected behavior

Should be able to communicate with guest without needing the VmId. @benhillis As per your comment here: https://github.com/microsoft/WSL/issues/4131#issuecomment-502287479 , is there a way now for host/guest communication? Thanks in advance.

Actual behavior

Not working.

microsoft-github-policy-service[bot] commented 7 months ago

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!