Firejox

There is no option for it, this can be add as a feature in future.

Just provide a workaround. If you allow WSL2 distro able to execute Windows program, you can try this workaround https://github.com/microsoft/WSL/issues/8854#issuecomment-1490454734.

It is the Windows-defined virtual socket for `hyper-v` vm, and it will correspond to the `vsock` of Linux guest vm. There are some document for hyper-v socket development. [Make your...

After some testing, I think there is no need to develop under WSL2 environment. The only need is to add Hyper-V Socket functionality. Then Windows client will connect to the...

@totaam It comes from [the explanation in Linux kernel code](https://github.com/torvalds/linux/blob/7e364e56293bb98cae1b55fd835f5991c4e96e7d/net/vmw_vsock/hyperv_transport.c#L141-L157) > ```c > /**************************************************************************** > * The only valid Service GUIDs, from the perspectives of both the host and *...

> > it is hard to keep thread-safe during switching and return dead fiber back to stackpool. > > Thanks for the detailed solution, but could you detail the problem...