This repository has been archived by the owner on May 12, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 375
It will take much more time to launch kata when both vsock and template enabled #1055
Comments
lifupan
added a commit
to lifupan/kata-runtime
that referenced
this issue
Dec 19, 2018
Vsock conflicts with factory, when both of them are enabled, kata will try to create a new vm template which is useless, thus it's better to disable template to save a lot of time. Fixes: kata-containers#1055 Signed-off-by: fupan <lifupan@gmail.com>
lifupan
added a commit
to lifupan/kata-runtime
that referenced
this issue
Dec 19, 2018
Vsock conflicts with factory, when both of them are enabled, kata will try to create a new vm template which is useless, thus it's better to disable template to save a lot of time. Fixes: kata-containers#1055 Signed-off-by: fupan <lifupan@gmail.com>
lifupan
added a commit
to lifupan/kata-runtime
that referenced
this issue
Dec 19, 2018
Vsock conflicts with factory, when both of them are enabled, kata will try to create a new vm template which is useless, thus it's better to return an error directly to let users know that those two config cannot be enabled at the same time. Fixes: kata-containers#1055 Signed-off-by: fupan <lifupan@gmail.com>
devimc
pushed a commit
to devimc/kata-runtime
that referenced
this issue
Dec 19, 2018
Vsock conflicts with factory, when both of them are enabled, kata will try to create a new vm template which is useless, thus it's better to return an error directly to let users know that those two config cannot be enabled at the same time. Fixes: kata-containers#1055 Signed-off-by: fupan <lifupan@gmail.com>
mcastelino
pushed a commit
to mcastelino/runtime-1
that referenced
this issue
Dec 19, 2018
Vsock conflicts with factory, when both of them are enabled, kata will try to create a new vm template which is useless, thus it's better to return an error directly to let users know that those two config cannot be enabled at the same time. Fixes: kata-containers#1055 Signed-off-by: fupan <lifupan@gmail.com>
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
Description of problem
vsock conflicts with factory, when both of them are enabled, kata will try
to create a new vm template, then use this template to launch another qemu
process. But this template is useless when try to launch other kata containers.
Thus it's better to disable template when vsock enabled to save a lot of boot time.
Expected result
(replace this text with an explanation of what you thought would happen)
Actual result
(replace this text with details of what actually happened)
(replace this text with the output of the
kata-collect-data.sh
script, afteryou have reviewed its content to ensure it does not contain any private
information).
The text was updated successfully, but these errors were encountered: