Tuesday, 2021-11-30

kata-irc-bot<feng.wang> The error message is originated from the mount.rs in the kata agent. I wonder if it has something to do with the kernel-experimental build.01:39
kata-irc-bot<bergwolf> any error from guest dmesg?03:12
kata-irc-bot<bergwolf> you can get it from guest debug console, or from the agent log03:12
kata-irc-bot<shuo.chen> @bergwolf do you know the best way in kata vm to view the agent log?04:40
kata-irc-bot<feng.wang> @bergwolf Because the container cannot start, the guest doesn’t live long enough for me to log into it. Where can I see the agent log?05:21
kata-irc-bot<bergwolf> If you enable containerd debug mode and all kata debug options, you can see the log in containerd's log05:58
kata-irc-bot<bergwolf> @shuo.chen @feng.wang ^^05:58
kata-irc-bot<feng.wang> Thanks @bergwolf The agent debug seems garbled: ```Nov 30 07:09:56 aks-daxtest-14325650-vmss000000 kata[26479]: time="2021-11-30T07:09:56.909261221Z" level=debug msg="reading guest console" console-protocol=unix console-url=/run/vc/vm/ee5d800e5383236f80eec973c712db8cf5edb40cca91e0257fb4415707e 00405/console.sock name=containerd-shim-v2 pid=26479 sandbox=ee5d800e5383236f80eec973c712db8cf5edb40cca91e0257fb4415707e0040507:13
kata-irc-botsource=virtcontainers subsystem=sandbox vmconsole="[    0.665492] virtiofs: Unexpec{\"msg\":\"mounting07:13
kata-irc-botstorage\",\"level\":\"INFO\",\"ts\":\"2021-11-30T07:09:56.893475347+00:00\",\"subsystem\":\"mount\",\"name\":\"kata-agent\",\"pid\":\"91\",\"version\":\"0.1.0\",\"source\":\"agent\",\"storage-type\":\"virtio-fs\",\"mount-options\":\"dax=always\",\"mount-source:\":\"kataShared\",\"mount-fstype\":\"virtiofs\",\"mount-destination\":\"/run/kata-containers/shared/containers/\"}ted value for 'd"                                                       07:13
kata-irc-bot                                                     Nov 30 07:09:56 aks-daxtest-14325650-vmss000000 containerd[1204]: time="2021-11-30T07:09:56.909261221Z" level=debug msg="reading guest console" console-protocol=unix console-url=/run/vc/vm/ee5d800e5383236f80eec973c712db8cf5edb40cca91e0257fb441 5707e00405/console.sock name=containerd-shim-v2 pid=26479 sandbox=ee5d800e5383236f80eec973c712db8cf5edb40cca91e0257fb4415707e0040507:13
kata-irc-botsource=virtcontainers subsystem=sandbox vmconsole="[    0.665492] virtiofs: Unexpec{\"msg\":\"mounting storage\" ,\"level\":\"INFO\",\"ts\":\"2021-11-30T07:09:56.893475347+00:00\",\"subsystem\":\"mount\",\"name\":\"kata-agent\",\"pid\":\"91\",\"version\":\"0.1.0\",\"source\":\"agent\",\"storage-type\":\"virtio-fs\",\"mount-options\":\"dax=always\",\"moun07:13
kata-irc-bott-source:\":\"kataShared\",\"mount-fstype\":\"virtiofs\",\"mount-destination\":\"/run/kata-containers/shared/containers/\"}ted value for 'd"  ```07:13
kata-irc-bot<feng.wang> Note: I change the mount flag from `-o dax` to `-o dax=always`, which shouldn’t matter anyway.07:17
kata-irc-bot<bergwolf> you need to check the kernel code to find out which mount parameter is proper here imo07:41
kata-irc-bot<fidencio> Folks, kata-containers 2.3.0 has been released Yesterday!08:16
kata-irc-bot<feng.wang> This seems to be ultimate error message: ```Nov 30 17:09:11 aks-daxtest-14325650-vmss000000 kata[28012]: time="2021-11-30T17:09:11.992784886Z" level=debug msg="reading guest console" console-protocol=unix console-url=/run/vc/vm/d1d18faae31611be77d51c8716eefb0f01a9ded2941b4df790d252e9e53bc84d/console.sock name=containerd-shim-v2 pid=28012 sandbox=d1d18faae31611be77d51c8716eefb0f01a9ded2941b4df790d252e9e53bc84d source=virtcontainers17:10
kata-irc-botsubsystem=sandbox vmconsole="[    0.704896] virtio-fs: dax can't be enabled as filesystem device does not support it."``` 17:10
kata-irc-bot<feng.wang> It’s added in a recent kernel patch: https://patchwork.kernel.org/project/linux-fsdevel/patch/20210209224754.GG3171@redhat.com/ What does it mean the filesystem device doesn’t support it?17:13

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!