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

Update cc-env to include hypervisor version string #500

Closed
jodh-intel opened this issue Aug 31, 2017 · 0 comments
Closed

Update cc-env to include hypervisor version string #500

jodh-intel opened this issue Aug 31, 2017 · 0 comments
Assignees

Comments

@jodh-intel
Copy link
Contributor

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).

@jodh-intel jodh-intel self-assigned this Sep 1, 2017
mcastelino pushed a commit to mcastelino/runtime that referenced this issue Dec 6, 2018
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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant