WEI

Another error reported. My machine can run clear-container successfully, something wrong about my qemu version(1.5.3)? ``` $sudo runv --kernel /var/lib/hyper/kernel --initrd /var/lib/hyper/hyper-initrd.img run ubuntu E0825 09:59:39.162677 20412 qemu_process.go:153] (process:20425): GLib-WARNING...

The qemu works now, but runv failed again by followed the steps in README. I believe the instructions in README is not completed and will misguide new users. ``` $runv...

It works now. I suggest we should put below sample into "Run" section in README.md (https://github.com/hyperhq/runv#run). ``` mkdir mycontainer; cd mycontainer mkdir rootfs runv spec sudo docker export $(sudo docker...

Hi @laijs , I use runv as my dockerd runtime, failed to start container, no clear error log showed. My docker version is 17.03.2-ee-5, it tested with clear container successfully....

``` $/usr/bin/runv --version runv version 0.8.1, commit: v1.0.0-rc2-14-g99936bd $ls /var/log/runv ls: cannot access /var/log/runv: No such file or directory ```

Please see my last post. runv and kernel/initrd all is the newest version, compiled by myself.

Thanks @laijs , it works with docker 17.06.1-ee. I tried to limiting the cpu and memory, it seems memory limit is correct, but --cpusets-cpu doesn't work, is this normal? My...

Ok, understood. What about "docker run --cpus"? Does runv have a way to limiting the number of VCPUs? @laijs