Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

vsock: initiate a quick handshake to avoid VSOCK_DEFAULT_CONNECT_TIMEOUT #775

Closed
Pennyzct opened this issue Apr 30, 2020 · 0 comments
Closed

vsock: initiate a quick handshake to avoid VSOCK_DEFAULT_CONNECT_TIMEOUT #775

Pennyzct opened this issue Apr 30, 2020 · 0 comments
Labels
bug Incorrect behaviour needs-review Needs to be assessed by the team.

Comments

@Pennyzct
Copy link
Contributor

Related issues: kata-containers/runtime#1917
@Pennyzct Pennyzct added bug Incorrect behaviour needs-review Needs to be assessed by the team. labels Apr 30, 2020
Pennyzct added a commit to Pennyzct/agent that referenced this issue Apr 30, 2020
@Pennyzct
vsock: initiate a quick handshake to avoid VSOCK_DEFAULT_CONNECT_TIMEOUT
aa08bb9 
We will suffer default two seconds timeout, when kata-runtime initiates
a connection to agent server, and right now vsock transport in guest part
isn't ready.
Here, taking advices from Stefan Hajnoczi, we will do a quick handshake
to ensure host initiating connection until vsock device is completely ready.
The quick handshake follows below steps:
1. kata-runtime listens on a vsock port
2. agent.vsock_host_port=PORT is added to the kernel command-line options
3. kata-agent parses the port number and connects to the host
This commit covers the third part in kata-agent.

Fixes: kata-containers#775

Signed-off-by: Penny Zheng <penny.zheng@arm.com>
@Pennyzct Pennyzct mentioned this issue Apr 30, 2020
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Incorrect behaviour needs-review Needs to be assessed by the team.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

vsock: initiate a quick handshake to avoid VSOCK_DEFAULT_CONNECT_TIMEOUT(WIP) Pennyzct/agent
2 participants
@jodh-intel @Pennyzct