-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running gvisor-tap-vsock with dgram socket for Apple Virtualization #116
Comments
We are successfully using gvisor-tap-vsock+Code-Hex/vz in crc. However, we are not making use of https://developer.apple.com/documentation/virtualization/vzfilehandlenetworkdeviceattachment?language=obj , the main reason for that being that I only noticed it after having implemented differently, and I haven't had time to revisit this yet. How this works in crc is that we run https://github.com/containers/gvisor-tap-vsock/tree/main/cmd/vm in the VM. This creates a TAP network device to capture all the VM network traffic, and then forwards it to the host over virtio vsock. On the host, the data comes over a unix socket which is then used by gvisor-tap-vsock. |
Ah nice. I missed that creating tap and forwarding via vsock. |
Yeah, it's definitely a different model, it should be possible to get gvisor-tap-vsock to work with https://developer.apple.com/documentation/virtualization/vzfilehandlenetworkdeviceattachment?language=objc without making any changes to the VM image itself. |
Thanks a lot for the reference.
gvisor gets terminated with the following error
|
Looks like this issue got resolved with latest gvisor and it is working via vz network attachment well. Am happy to raise a PR as well for the same. |
This issue is fixed as part of #135 |
Hi
I am trying to use gvisor-tap-vsock with VM Started by Apple Virtualization API.
I was able to get the network up and running.
Working example code
https://github.com/mac-vz/vz/tree/gvisor
How it is integrated now?
But i noticed couple of issues like,
If feel the way i create dgram / wrapping of UDPConn is the cause for these issues. Any help around here would help a lot.
Am happy to even provide a PR for official support after fixing issues :-)
Thanks in advance.
The text was updated successfully, but these errors were encountered: