Skip to content
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

hybrid vsock lost the first package when it was just created #1432

Closed
teawater opened this issue Nov 26, 2019 · 3 comments
Closed

hybrid vsock lost the first package when it was just created #1432

teawater opened this issue Nov 26, 2019 · 3 comments
Labels
Priority: High Indicates than an issue or pull request should be resolved ahead of issues or pull requests labelled Type: Bug Indicates an unexpected problem or unintended behavior

Comments

@teawater
Copy link

teawater commented Nov 26, 2019

We meet the issue with firecracker in kata-containers/kata-containers#79.
And I found that hybrid vsock will drop or truncate the first package and qemu doesn't have this issue.
I add code that send an empty package and wait the first package arrive from client to handle this issue in alipay/grpc@811660d.

@sandreim
Copy link
Contributor

sandreim commented Nov 26, 2019

Thanks for logging this @teawater. We will look into it and update you.

@sandreim sandreim added Feature: IO Virtualization Priority: High Indicates than an issue or pull request should be resolved ahead of issues or pull requests labelled Type: Bug Indicates an unexpected problem or unintended behavior labels Nov 26, 2019
@sandreim
Copy link
Contributor

@teawater We need more context into the problem as our integration tests pass without requiring the workaround that you implemented. Can you please provide steps and some more information on the setup that reproduces this issue ? Ideally that would be the most simple scenario that triggers the bug.

@teawater
Copy link
Author

@sandreim Thanks for your comments.
I found that this is an issue of kata. I just post a PR to fix this issue in kata-containers/agent#696

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: High Indicates than an issue or pull request should be resolved ahead of issues or pull requests labelled Type: Bug Indicates an unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

2 participants