Peng Tao

It seems the container was killed by OOM killer. Can you retry with something like the `--memory 512MB` option?

@telala `runv` itself is an OCI runtime that is at the same layer as docker `runc` and the [nvidia docker runtime](https://github.com/NVIDIA/nvidia-container-runtime). They all can be specified through the `docker run...

@telala It is actually the job of [hyperstart](https://github.com/hyperhq/hyperstart) to create containers in a guest. There is no docker stack in the guest and thus no concept of a runtime there...

@telala do you mean the gpu kernel driver? You need to include it in the initrd image, by either building it in your guest kernel, or putting it in as...

@telala No, I'm afraid not. You have to use the same kernel (in the guest) that the nvidia.ko was built upon. Mismatching kernel versions can either prevent you from loading...

@telala Yes, you can use your own kernel, and re-create an initrd based on it. If you look at https://github.com/hyperhq/hyperstart/blob/master/build/make-initrd.sh, you can see how initrd is created. Replace with your...

@telala Is the above log from guest kernel? If so, my guess is that the gpu device is not properly passthrough to the guest. Care to send your gpu passthrough...

@telala no, devtmpfs is not mount namespace aware. Containers get the same view of devtmpfs as hyperstart. Can you mknod the device? The log only prints device major, can you...

@oilbeater Thanks a lot! I agree that it is better to keep netns and addresses on the tap device for compatibility with other container runtimes. As for the pod annotation...

@oilbeater Fair enough. We can make it (the annotation entirely) a config option for containerd so that kata can request different nic types via runtime handler config. Something like `runtime_cni_annotations...