-
Notifications
You must be signed in to change notification settings - Fork 610
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
VM network hang and panic on restart (gvisor-tap-vsock/pkg/tap.(*Switch).Accept
)
#1358
Comments
This seems a bug, although irrelevant to the topic here. |
Looking at the backtrace:
The crash happens at https://github.com/containers/gvisor-tap-vsock/blob/5b1aff8ba74374aeb62eaa06faa496faf2c56d74/pkg/tap/switch.go#L83 which tries to print Line 90 in f086bc4
Lines 38 to 46 in f086bc4
If this is reproducible, might be worth taking a closer look at this |
gvisor-tap-vsock/pkg/tap.(*Switch).Accept
)
This should not happen in current master. |
Thanks @balajiv113 |
Observing loss of connectivity to a lima VM after several hours using VZ and vmnet shared network. VM fails to
stop
cleanly, requiringlimactl stop -f
. Subsequently starting the VM results in panic from gvisor-tap-socket. A secondstop -f
and start results in successful VM boot. Possibly related to containers/gvisor-tap-vsock#161limactl version HEAD-eb49205
socket_vmnet: stable 1.1.1
M2 MacBook Air
Ventura (13.1)
lima.yaml
The text was updated successfully, but these errors were encountered: