You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 6, 2020. It is now read-only.
Curently, the cc-env command shows component versions but does not include the hypervisor version (although it does show the hypervisor path and machine type).
Once clearcontainers/qemu#2 lands, we can supplement the output to include the full hypervisor version string (including the short commit for the branch).
The text was updated successfully, but these errors were encountered:
For each time a sandbox structure is created, we ensure s.Release()
is called. Then we can keep the qmp connection as long as Sandbox
pointer is alive.
All VC interfaces are still stateless as s.Release() is called before
each API returns.
OTOH, for VCSandbox APIs, FetchSandbox() must be paired with s.Release,
the same as before.
Fixes: clearcontainers#500
Signed-off-by: Peng Tao <[email protected]>
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Curently, the
cc-env
command shows component versions but does not include the hypervisor version (although it does show the hypervisor path and machine type).Once clearcontainers/qemu#2 lands, we can supplement the output to include the full hypervisor version string (including the short commit for the branch).
The text was updated successfully, but these errors were encountered: