Thursday, 2019-09-26

*** igordc has joined #kata-dev00:44
*** changcheng has joined #kata-dev02:16
*** igordc has quit IRC03:18
*** igordc has joined #kata-dev03:18
*** pcaruana has joined #kata-dev06:30
*** igordc has quit IRC06:53
*** tmhoang1 has joined #kata-dev06:59
*** sgarzare has joined #kata-dev07:08
*** sameo has joined #kata-dev07:29
*** jodh has joined #kata-dev07:30
*** davidgiluk has joined #kata-dev08:02
*** lpetrut has joined #kata-dev08:49
*** pcaruana has quit IRC10:32
*** pcaruana has joined #kata-dev10:58
*** pcaruana has quit IRC12:05
*** tmhoang1 has quit IRC12:07
*** devimc has joined #kata-dev12:17
*** pcaruana has joined #kata-dev12:19
*** fuentess has joined #kata-dev12:27
*** tobberydberg_ is now known as tobberydberg13:01
*** tmhoang1 has joined #kata-dev13:49
davidgilukdoes someone know where the kata alpha builds with virtiofs are - I'd like to try debugging the existing staticly built virtiofsd15:36
kata-irc-bot1<salvador.fuentes> hi davidgiluk, you can find the assets here: https://github.com/kata-containers/runtime/releases/tag/1.9.0-alpha215:38
kata-irc-bot1<salvador.fuentes> I just needed to apply runtime PR 1994 and rebuild kata-runtime15:39
davidgiluksalvador.fuentes: Ah excellent, I want to see if I can see what's going on with your static build15:39
kata-irc-bot1<salvador.fuentes> btw, I've just tested the patch you provided on the PR and still cannot make virtiofsd work15:39
kata-irc-bot1<salvador.fuentes> thanks davidgiluk15:40
davidgiluksalvador.fuentes: OK, can you pass -d to virtiofsd to see if it'll spit out any more debug?  Also, which kernel are you on?15:40
kata-irc-bot1<salvador.fuentes> sure, I'll try with -d15:41
kata-irc-bot1<salvador.fuentes> my kernel is 5.0.0-101815:41
davidgilukok, so that's a nice new one, not the same problem Naresh had, which was an older crusty kernel15:46
fuentessdavidgiluk: I've tested virtiofsd with -d and still no more information, updated the PR with this comment as well15:57
*** pcaruana has quit IRC15:57
*** eernst has joined #kata-dev15:58
davidgilukfuentess: Hmm I wonder where the output goes, with -d it should be quite chatty15:58
*** eernst has quit IRC15:59
fuentessdavidgiluk: this is the command being run: /opt/kata/bin/virtiofsd --fd=3 -o source=/run/kata-containers/shared/sandboxes/14b49f4045a185eaaf84b3aaff63ff2f0fa683874c4dfbb61a75a9e3822c54e5 -o cache=always --syslog -d -f15:59
davidgilukyou'd hope it's all piled into syslog16:02
kata-irc-bot1<claire> Hey y’all! If you’re interested in helping to create a Kata user survey - @allison @jimmy and I are available for a kickoff discussion about it on October 9th at 10:00am PT. If that works for you, please let us know this week and we’ll get it booked. Thanks!16:07
*** tmhoang1 has quit IRC16:13
*** igordc has joined #kata-dev16:14
davidgilukfuentess: Oh that audit message makes more sense!16:19
davidgilukfuentess: Whenever seccomp gets invoked it just nukes the process completely before it gets a chance to log anything16:34
kata-irc-bot1<eric.ernst> seccomp is the worst :)16:35
kata-irc-bot1<eric.ernst> (or the best)16:35
kata-irc-bot1<eric.ernst> Seems profile isn't appropriate then?16:35
davidgilukeric.ernst: So, hmm who is setting up the seccomp at the point virtiofsd is run - before it sets up it's own?16:36
kata-irc-bot1<eric.ernst> I think it is its own -- we don't apply any.16:36
davidgilukhmm and my reading is we don't set it up until after we've done the listen() call though16:38
kata-irc-bot1<eric.ernst> should be a simple enough test to just remove the seccomp handling in virtiofsd to see?16:39
davidgilukyeh I just suggested in the bug to add the listen() call to the seccomp list16:40
*** igordc has quit IRC16:43
davidgilukfuentess: Note that the static tar has a /opt/kata/bin/virtiofsd and an /opt/kata/bin/virtiofsd-x86_64 which is ~4 months older16:53
*** lpetrut has quit IRC16:53
fuentessdavidgiluk: thanks for the suggestion, I'm trying it now16:53
fuentessdavidgiluk: yeah, I think the old one is the one that works with the old implementation, which uses nemu in our case16:54
davidgilukfuentess: I'm going to be surprised if it fixes it, because in theory the listen we do is before we invoke seccomp; unless there's another listen somewhere, and then ...why?16:54
davidgilukok, replicated it here17:00
*** jodh has quit IRC17:00
*** dklyle has quit IRC17:01
*** dklyle has joined #kata-dev17:01
davidgilukthat makes no sense17:11
davidgilukI see  a coredump of virtio_loop->fuse_info->__vsyslog_chk->time  and that's where it gets the sigsys of apparently a listen call - wth would you do a listen in time()17:12
davidgilukfuentess: OK, I think I see it17:14
davidgilukfuentess: on x86 201 is actually _NR_time - not listen17:14
fuentessdavidgiluk: ooh, ok, great. so the listen change would work?17:15
fuentessstill building it with the change here...17:15
davidgilukfuentess: Cancel that, the listen change wont help, it needs to be time() not listen()17:15
davidgilukfuentess: Now, the next question is why your static build hits it17:16
fuentessdavidgiluk: ok, cancelling and tryint with time17:16
fuentessyeah, only happens on static build17:16
davidgilukfuentess: I think the dynamic version gets clever and uses something from the vdso to do time() calls, the static version is....static17:18
*** igordc has joined #kata-dev17:28
fuentessdavidgiluk: yeah, that fixes the issue17:31
fuentessI can launch qemu successfully with virtiofsd17:31
fuentessthanks for the help17:31
davidgilukwahey!17:32
fuentessdavidgiluk: once you add the patch, can you please share it, so that we can grab it and apply it when builiding it?17:34
davidgiluksure, will do17:34
fuentessdavidgiluk: thank you :)17:35
davidgilukyou want a patch against 0.3?17:37
*** sgarzare has quit IRC17:38
fuentessdavidgiluk: that would be great17:38
davidgilukseccomp lists are quite tricky, because you never quite know what another version of a library you link against is going to use17:47
*** pcaruana has joined #kata-dev18:04
*** sameo has quit IRC18:04
*** igordc has quit IRC18:29
*** igordc has joined #kata-dev18:32
*** pcaruana has quit IRC18:36
*** eernst has joined #kata-dev18:46
*** eernst has quit IRC18:51
*** eernst_ has joined #kata-dev18:51
*** eernst_ has quit IRC18:51
*** eernst has joined #kata-dev18:51
*** davidgiluk has quit IRC19:12
*** lpetrut has joined #kata-dev19:47
*** lpetrut has quit IRC19:58
kata-irc-bot1<kshitij> Hi I have a question regarding ARP replies on virtual endpoints. I have an interface mgmt0 from which I ping another interface. I can see in “ifconfig” Tx and Rx stats going up . On the host in the bridge I can see the MAC addresses being learnt and reply packets reaching mgmt0. However, I don’t see ARP resolved in the container. Am I missing something? I have a custom build initrd (added Priority field to the Route struct)20:34
*** devimc has quit IRC21:16
*** fuentess has quit IRC21:37
*** sameo has joined #kata-dev22:10
*** sameo has quit IRC22:21
*** sameo has joined #kata-dev22:32
*** eernst has quit IRC23:01
*** eernst has joined #kata-dev23:04
*** eernst has quit IRC23:08
*** sameo has quit IRC23:48

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!