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

kata+firecracker: boot of agent takes 3.5 seconds #1160

Open
egernst opened this issue Jan 23, 2019 · 4 comments

Comments

Projects
None yet
4 participants
@egernst
Copy link
Contributor

commented Jan 23, 2019

Boot time to the Kata-Agent is around 3.5 seconds, per open-tracing tracing output.

Taking a looking at the kernel boot, nothing is notable with respect to boot. It seems that the latency is in userspace as we await for the gRPC server to come up and respond to kata-runtime on the host.

@jodh-intel

This comment has been minimized.

Copy link
Contributor

commented Jan 23, 2019

It would be worth enabling full debug and looking to see when the agents announce message appears.

@egernst

This comment has been minimized.

Copy link
Contributor Author

commented Mar 12, 2019

Manohar is betting money this is an entropy issue. Need to find someone to confirm so he can collect his winnings.

/cc @mcastelino

@egernst egernst added the help wanted label Mar 12, 2019

@sboeuf

This comment has been minimized.

Copy link
Contributor

commented Mar 12, 2019

@mcastelino if this is confirmed, what would be the plan to fix it? virtio-rng would need to be added to the FC device model, right?

@grahamwhaley

This comment has been minimized.

Copy link
Member

commented Mar 12, 2019

/me backs @mcastelino bet for entropy....

@jodh-intel jodh-intel removed the help wanted label Jun 4, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.