virtcontainers
virtcontainers copied to clipboard
A Go package for building hardware virtualized container runtimes
The container and pod configuration structures do not yet contain isolation descriptions. The isolation structures are not defined.
Shut the QMP socket down and clean the qmp listen routine when pod.startPod() is done
`startCCShimStartWithoutConsoleSuccessful()` messes with standard streams and if the following two tests are not disabled, running the unit tests locally will hang forever: - `TestCCShimStartSuccessful` - `TestCCShimStartDetachSuccessful`
Switch tests to use a testing framework that provides fixtures (test setup / tear down functions).
The tests are currently using the `testing` package, but http://labix.org/gocheck is much more powerful (and compatible with `testing`). Crucially the latter offers test fixtures like `SetUpTest()` and `TearDownTest()` to simplify...
The `virtc` binary does not provide a `container kill` feature meaning `KillContainer()` cannot be tested at the functional level in isolation from the runtime (which exercises it via `cc-runtime kill`)....
We need to grow a set of `virtc` [BATS](https://github.com/sstephenson/bats) tests run by the CI which exercise all API calls. Related: #495.
Now that we've increased the runtime unit-test coverage, we should probably re-assess the virtcontainers level of coverage which is now lower than the runtime by some margin.
Currently we set the default number of VCPUs to be 1: https://github.com/containers/virtcontainers/blob/master/hypervisor.go#L36 This is one obvious and safe default, but from some testing (under https://github.com/clearcontainers/runtime), it seems that running up...
``` $ sudo virtc container create --pod-id=34d33aa0-b9cb-4a4e-ba61-d063fcaaa144 --rootfs=/home/james/tmp/oci --cmd sh -id foo --console /dev/pts/4 INFO[0000] Info structure: {ID:34d33aa0-b9cb-4a4e-ba61-d063fcaaa144 Hooks:{PreStartHooks:[] PostStartHooks:[] PostStopHooks:[]} VMConfig:{VCPUs:0 Memory:0} HypervisorType:qemu HypervisorConfig:{KernelPath:/usr/share/clear-containers/vmlinux.container ImagePath:/usr/share/clear-containers/clear-containers.img HypervisorPath: KernelParams:[] HypervisorParams:[] HypervisorMachineType:pc-lite...
_From @jcvenegas on May 11, 2017 14:2_ _From @jodh-intel on February 17, 2017 16:59_ We need to consider making the hypervisor shutdown automatically if it detects that either the proxy...