-
After I use ctrl+c to terminate
And if I run
Why does this happen? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
I've experienced the exactly same issue. At the first execution right after reboot, running ./vhive aborts with "failed to listen" error. It aborts with "Bridge could not be created" from next executions. |
Beta Was this translation helpful? Give feedback.
-
@facelessq @sosson97 thank you for the questions. Upon start, vHive needs to connect to the firecracker-containerd daemon to control the lifecycle of VMs. If vHive was terminated abnormally, some host resources might not be cleaned up. Particularly, the unix socket file as in the first log and the bridges as in the second example. Bridges are normally created upon a vHive start so that VMs's taps can be connected to the host interface via a bridge. Note that taps and bridges are created by vHive directly and not by the CNI plugin. Solution:
Another recommendation is to use |
Beta Was this translation helpful? Give feedback.
@facelessq @sosson97 thank you for the questions.
Upon start, vHive needs to connect to the firecracker-containerd daemon to control the lifecycle of VMs. If vHive was terminated abnormally, some host resources might not be cleaned up. Particularly, the unix socket file as in the first log and the bridges as in the second example. Bridges are normally created upon a vHive start so that VMs's taps can be connected to the host interface via a bridge. Note that taps and bridges are created by vHive directly and not by the CNI plugin.
Solution:
./scripts/github_runner/clean_cri_runner.sh