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 12, 2021. It is now read-only.
We always call waitSandbox after we start the VM (startSandbox), so
let's simplify the hypervisor interface and integrate waiting for the VM
into startSandbox.
This makes startSandbox a blocking call, but that is practically the
case today.
Fixes: kata-containers#1009
Signed-off-by: Samuel Ortiz <[email protected]>
sameo
pushed a commit
to sameo/runtime-1
that referenced
this issue
Dec 18, 2018
We always call waitSandbox after we start the VM (startSandbox), so
let's simplify the hypervisor interface and integrate waiting for the VM
into startSandbox.
This makes startSandbox a blocking call, but that is practically the
case today.
Fixes: kata-containers#1009
Signed-off-by: Samuel Ortiz <[email protected]>
sameo
pushed a commit
to sameo/runtime-1
that referenced
this issue
Jan 8, 2019
We always call waitSandbox after we start the VM (startSandbox), so
let's simplify the hypervisor interface and integrate waiting for the VM
into startSandbox.
This makes startSandbox a blocking call, but that is practically the
case today.
Fixes: kata-containers#1009
Signed-off-by: Samuel Ortiz <[email protected]>
Description of problem
The virtcontainers hypervisor interface is complex and includes redundant or vaguely defined methods.
The text was updated successfully, but these errors were encountered: