Skip to content

re-running sudo ./vhive issue #204

Answered by ustiugov
facelessq asked this question in Q&A
Discussion options

You must be logged in to vote

@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:

  1. Clean up: ./scripts/github_runner/clean_cri_runner.sh
  2. Restart the cluster, following the instructions for a single-node cluster. We don't have a set …

Replies: 2 comments 5 replies

Comment options

You must be logged in to vote
5 replies
@ustiugov
Comment options

@sosson97
Comment options

@ustiugov
Comment options

@sosson97
Comment options

@ustiugov
Comment options

Comment options

You must be logged in to vote
0 replies
Answer selected by ustiugov
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants