Tuesday, 2021-02-23

*** crobinso has quit IRC01:06
*** sameo has joined #kata-dev06:19
*** dklyle has quit IRC07:57
*** sgarzare has joined #kata-dev07:57
*** fgiudici has joined #kata-dev08:12
*** jodh has joined #kata-dev08:27
*** fgiudici_ has joined #kata-dev08:51
*** fgiudici has quit IRC08:51
*** davidgiluk has joined #kata-dev09:01
*** fgiudici_ has quit IRC09:04
*** fgiudici has joined #kata-dev09:04
*** fgiudici has quit IRC09:25
*** fgiudici has joined #kata-dev09:25
*** ailan has joined #kata-dev09:33
*** devimc has joined #kata-dev13:05
*** crobinso has joined #kata-dev13:37
*** fuentess has joined #kata-dev14:04
*** jodh has quit IRC14:11
*** jodh has joined #kata-dev14:20
devimcHi davidgiluk,14:53
devimcqq,  how can I debug virtiofs ?14:53
davidgilukdevimc: Ah, well, how did you break it?14:54
devimcdavidgiluk, running cloud-hypervisor + kata + knative14:54
devimcany operation on the shared directory is getting stuck14:55
davidgilukthat's an exciting combination - are you running the C daemon or the rust daemon?14:55
devimcdavidgiluk, for example  ls /run/kata-containers/shared/containers14:55
devimcis getting stuck14:55
devimcdavidgiluk, C daemon14:55
davidgilukdevimc: Stuck normally means the daemon has crashed, so if you have a core or something then that would be great, if not then you can try running the daemon with -o debug   and see what it's dieing breath is14:56
devimcdavidgiluk, thx, let me enable core file dumps14:57
davidgilukdevimc: With all the sandboxing, finding where and if core dumps actually land can be tricky14:58
devimcdavidgiluk, ok, I will use strace then14:59
davidgilukdevimc: That's a bit desperate; before doing that, I'd check /var/log/audit to see if there are any seccomp warns if you've tripped across a missing syscall15:01
devimcdavidgiluk, type=ANOM_ABEND msg=audit(1611606817.326:32314): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=38414 comm="pool" exe="/opt/kata/bin/v15:05
devimcirtiofsd" sig=11 res=115:05
devimcI guess sig is signal15:05
davidgiluksniff, a segfault15:06
devimc:(15:07
davidgilukdevimc: Then a core or gdb is probably best, although a -o debug might make it obvious15:07
devimcdavidgiluk, really hard to find the log, since this is a scalability issue15:07
davidgilukdevimc: Can you get a gdb to it before it crashes?15:07
devimcdavidgiluk, sure, I will enable core file dump15:08
kata-irc-bot<eric.ernst> devimc, is this with dax?15:15
*** dklyle has joined #kata-dev15:16
devimcdavidgiluk, I think DAX is disabled15:17
devimcvirtio_fs_cache_size = 015:17
davidgilukyeh15:18
kata-irc-bot<eric.ernst> How often/quickly does this manifest?15:19
devimcall the time when running iostio + knative15:20
devimc*istio15:21
kata-irc-bot<eric.ernst> Having an issue is bad, but at least its easy to reproduce.15:21
davidgiluknod, repeatable crashes are lovely15:21
davidgilukdevimc: Does it crash immediately on connect or later?15:22
kata-irc-bot<eric.ernst> I'm glad you're seeing this with CLH as well; its a bit easier for initial logs/debug. Can you repro same setup with qemu?15:22
devimcdavidgiluk, latter, when envoy runs15:22
devimcenvoy is the second container15:22
devimceach pod has 2 containers15:23
davidgilukdevimc: OK, so glue gdb to it, and then start your 2nd container15:26
kata-irc-bot<gabriela.cervantes.te> @eric.ernst yes, I am working on a PR to bring the latest changes to stable-2.0 for the CI15:43
devimcdavidgiluk, https://paste.centos.org/view/a94eb35015:58
devimccoredump is not really useful, I need to enable debug and rebuild it15:58
davidgilukdevimc: I'm not sure you've traced the interesting threads there16:15
devimcdavidgiluk, let me try again. now with virtiofsd symbols16:19
devimc*debug symbols16:19
*** pmores has joined #kata-dev16:33
kata-irc-bot<fidencio> @samuel.ortiz, out of curiosity, we talked about devicemapper on the meeting, but what's the devicemapper advantages over overlayfs? Or, maybe a better question, do you see performance impacts on someone using overlayfs instead of devicemapper? If so, why?16:51
pmoresHi! I'm wondering what keeps https://github.com/kata-containers/runtime/pull/3127 from being merged - it has approvals but several checks, marked as Required, seem to be Expected.17:01
pmoresConsidering that last changes to the PR seem to be almost two weeks old, is this OK?17:02
kata-irc-bot<eric.ernst> @fidencio -- just do an fio test using blk devcie and using virtiofs17:05
kata-irc-bot<eric.ernst> perf wise, virtio-blk > virtiofs (today)17:05
*** devimc has quit IRC17:20
*** devimc has joined #kata-dev17:21
kata-irc-bot<fidencio> We have to run /test there, Pavel.17:23
pmoresfidencio: thanks!17:25
*** fgiudici has quit IRC18:00
*** jodh has quit IRC18:00
*** ailan has quit IRC18:06
*** sgarzare has quit IRC18:23
kata-irc-bot<fidencio> @eric.ernst, @jose.carlos.venegas.m, do we have someone from firecracker community that we can loop into our issues?18:47
kata-irc-bot<eric.ernst> They've been pretty responsive / collaborative.19:06
kata-irc-bot<eric.ernst> Probably depends on the area of the issue.19:06
kata-irc-bot<fidencio> I've opened https://github.com/kata-containers/tests/issues/3268 and marked Penny there.19:18
kata-irc-bot<fidencio> If you think there's someone else that could help, please, mark the person19:19
kata-irc-bot<jose.carlos.venegas.m> @fidencio I may be wrong but I think @penny.zheng  is not doing a lot of kata recently19:35
kata-irc-bot<fidencio> Hmm. Let me open an issue on Firecracker then19:35
kata-irc-bot<fidencio> And ask for help on their community (as I did for acrn)19:35
kata-irc-bot<fidencio> Thanks, @jose.carlos.venegas.m!19:35
kata-irc-bot<jose.carlos.venegas.m> @fidencio, no problem, lets see if someone has some cycles there, else ask  if someone want to take ownership of the integration in kata19:36
kata-irc-bot<jose.carlos.venegas.m> it may be good to get in good shape the integration for the usecases that makesense for fc19:37
kata-irc-bot<jose.carlos.venegas.m> mostly kata + fass would be the main use case19:37
kata-irc-bot<fidencio> @gabriela.cervantes.te, @jose.carlos.venegas.m, let's talk a little bit about CI :slightly_smiling_face: :thread:19:42
kata-irc-bot<fidencio> I've noticed that the majority of our integration tests, if not all of them, depend on docker :slightly_smiling_face:19:42
kata-irc-bot<fidencio> I'm talking about `main` (so, 2.x) of the tests repo19:42
kata-irc-bot<fidencio> Can we just remove all of those?19:42
kata-irc-bot<jose.carlos.venegas.m> all jobs depending in docker?19:43
kata-irc-bot<fidencio> 1 minute, let me get links.19:43
kata-irc-bot<jose.carlos.venegas.m> I think most of the (it not all should depend as a way to build some assets) but we dont to any testing using docker19:43
kata-irc-bot<jose.carlos.venegas.m> I say because today kata 2.x is not compatible with any docker version19:44
kata-irc-bot<fidencio> We're not testing, but the tests are still there.  Take a look here: https://github.com/kata-containers/tests/tree/main/integration19:44
kata-irc-bot<fidencio> If you do a `git grep docker.*runtime`, you get: https://paste.centos.org/view/17c7d2ce19:45
kata-irc-bot<fidencio> All of those could be simply removed19:45
kata-irc-bot<fidencio> And I already removed docker and docker-composed ones19:46
kata-irc-bot<fidencio> Here's the full list of things that can be removed: https://paste.centos.org/view/cc0baf7e19:46
kata-irc-bot<jose.carlos.venegas.m> I see, yep there is a lot of them that are not running today, I am not sure what should be the best way.19:47
kata-irc-bot<fidencio> Argh! https://paste.centos.org/view/90ba72ea19:47
kata-irc-bot<jose.carlos.venegas.m> we could left them until the time docker is back, or remove them and if docker is back re add them19:47
kata-irc-bot<jose.carlos.venegas.m> @fidencio for some of those we are updating them to use ctr intead19:48
kata-irc-bot<fidencio> My suggestion is: 1. Open an issue about removing everything that's docker related and not tested on 2.x; 2. Remove everything, no mercy; 3. Create issues for evaluating what should be added again;19:49
kata-irc-bot<fidencio> IMHO, removing something not used at all and waiting for people to raise a complain (thus step 3) seems to work better than ask to remove19:49
kata-irc-bot<fidencio> And git, thankfully, allows us to get to those files quite easily if needed.19:50
kata-irc-bot<fidencio> (for those young kids who never used anything else but git,  you're spoiled! :-))19:50
kata-irc-bot<gabriela.cervantes.te> we can create a PR to remove all docker tests and maybe people can comment or hate the PR19:50
kata-irc-bot<jose.carlos.venegas.m> yeah, it is not that they will be gone forever19:50
kata-irc-bot<fidencio> Ack, let me open issues and submit a PR then!19:50
kata-irc-bot<gabriela.cervantes.te> ok thanks19:51
kata-irc-bot<fidencio> Thanks a lot for the input!19:51
*** crobinso has quit IRC20:10
kata-irc-bot<fidencio> Actually, I opened the issue but I'll not do the change right now as I realised it may be a good first issue for someone looking at the project.20:10
*** davidgiluk has quit IRC20:14
kata-irc-bot<jose.carlos.venegas.m> :slightly_smiling_face:20:19
kata-irc-bot<jose.carlos.venegas.m> we need a away to announce good first issues20:19
kata-irc-bot<jose.carlos.venegas.m> a weekly mail asking for help or a slack message20:19
kata-irc-bot<jose.carlos.venegas.m> some  youtube ads20:20
kata-irc-bot<fidencio> I'm trying to remember who of you people hooked me up into this project.20:24
kata-irc-bot<fidencio> I don't remember what was done, but somehow worked. :slightly_smiling_face:20:24
*** pmores has quit IRC21:12
*** sameo has quit IRC22:08
*** devimc has quit IRC22:09
*** kgz has quit IRC22:46
*** fidencio has quit IRC22:46
*** kgz has joined #kata-dev22:47
*** fidencio has joined #kata-dev22:48

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