Friday, 2018-06-29

*** LinuxMe has joined #kata-dev00:04
*** LinuxMe has quit IRC00:09
*** annabelleB has joined #kata-dev01:07
*** annabelleB has quit IRC01:09
*** fuentess has joined #kata-dev01:15
*** lamego_ is now known as lamego01:16
*** dlw has joined #kata-dev01:39
*** LinuxMe_ has joined #kata-dev01:46
*** annabelleB has joined #kata-dev02:11
*** LinuxMe_ has quit IRC02:13
*** annabelleB has quit IRC02:44
*** lamego has left #kata-dev02:50
*** LinuxMe has joined #kata-dev02:52
*** LinuxMe has quit IRC02:57
*** fuentess has quit IRC03:47
*** LinuxMe has joined #kata-dev04:00
*** LinuxMe has quit IRC04:05
*** sjas has joined #kata-dev04:21
*** sjas_ has quit IRC04:24
*** LinuxMe has joined #kata-dev05:00
*** LinuxMe has quit IRC05:04
*** annabelleB has joined #kata-dev05:18
*** annabelleB has quit IRC05:33
*** LinuxMe has joined #kata-dev06:29
*** LinuxMe has quit IRC06:35
*** sameo has joined #kata-dev07:00
*** LinuxMe has joined #kata-dev07:06
*** LinuxMe has quit IRC07:11
*** jodh has joined #kata-dev07:17
*** davidgiluk has joined #kata-dev08:02
*** gwhaley has joined #kata-dev08:05
*** cdent has joined #kata-dev08:53
*** LinuxMe has joined #kata-dev08:57
*** LinuxMe has quit IRC09:02
*** LinuxMe has joined #kata-dev09:34
stefanhaIs Kata supposed to work with modular kernels?  The rootfs Fedora script seems to be missing the systemd-udev package that will load drivers on demand.09:38
*** LinuxMe has quit IRC09:39
stefanhalsm5: ^09:43
stefanhalsm5: Have you tweaked to the Fedora rootfs script?09:44
gwhaley@stefanha - kernels, as in the VM kernels. Historically, ClearContainers did not support modules, but runv did iirc. I don't think we've enabled modules for Kata yet - but I think the agreement is that we probably will09:49
gwhaleywe would then I believe have to have a method (a mount) to get the modules dir mapped from the host into the guest, and ensure09:50
gwhaleywe have the right modules (versions) for that VM kernel.09:50
gwhaleyI have in the past suggested we should turn on module signing (the kernel module version check config), to try and ensure we don't try to load the wrong modules, which could cause a debug nightmare :-)09:50
stefanhagwhaley: I see.  The rootfs.sh KERNEL_MODULES_DIR= environment variable is working fine for me.  I used it to copy in the necessary kernel modules.09:51
stefanhakata-agent is running happily inside the VM with Fedora initramfs but for some reason docker + kata-runtime are waiting for something.  Eventually creating the container times out.09:52
* stefanha looks at the runtime09:53
* gwhaley not up to date on this - ah, so you can set that KERNEL_MODULES_DIR when doing an osbuilder rootfs build, and it will copy those modules into the rootfs image (rather than have them in a host side share that is mapped/mounted into the VM). That sounds like a good interim for allowing customised images with modules then.09:54
stefanhagwhaley: I've realized that the Fedora rootfs was not designed for initramfs.  It's several hundred MB large :-).  But at the moment this seems to work.09:55
stefanhaThe last log messages from kata-runtime are "VM started" and "proxy started".  Then the proxy logs kernel boot messages, followed by kata-agent startup messages.09:55
stefanhaAfter that, silence.09:55
* gwhaley goes to find ref for magic debug tricks...09:56
stefanhaI have enabled them according to the Developer Guide.09:56
stefanhaHopefully a backtrace from kata-runtime will contain useful info.09:56
gwhaleythen there is a debug console : https://github.com/kata-containers/documentation/blob/master/Developer-Guide.md#set-up-a-debug-console09:57
* gwhaley has not done that himself though09:57
jodhstefanha: yes, you can "kill -USR1 $runtime_pid" to get the backtrace but make sure you enable full debug for the system (see dev guide). But, if you're using the debug console, read that section carefully as you have to *disable* proxy debug for it to work.09:59
stefanhajodh: Thanks!10:00
*** zerocoolback has joined #kata-dev10:09
*** LinuxMe has joined #kata-dev10:11
*** LinuxMe has quit IRC10:15
stefanhaIs there a way to ping the agent from the host?10:29
stefanhaI see an HTTP2 request being sent by the proxy to kata.sock,10:30
stefanhabut no response.10:30
stefanha(The agent has started and is running inside the guest.)10:30
gwhaley@stfanha - not that I know of. /cc @jodh?10:31
*** zerocoolback has quit IRC10:31
stefanhaIt would be funny if Fedora's SELinux is stopping the agent :)10:33
stefanhaWill check that out10:33
*** zerocoolback has joined #kata-dev10:34
jodhstefanha: gwhaley: there is an api, but it's unused atm afaik - https://github.com/kata-containers/agent/blob/master/protocols/grpc/health.proto#L3610:34
gwhaleyhey @jodh, whilst you are here ;-) - do you know if the '--log=filename' option works for the kata runtime (I presume it does) - I'm trying to enable it via /etc/docker/daemon.json adding a runtime args, but not seeing any output yet10:36
gwhaleywill try harder...10:36
jodhgwhaley: are you trying to create separate kata-runtime logs for each "docker run"?10:37
gwhaleynot yet... just dumping them into a single file for a start. But, if it is easy to get separate ones for each run - then that would be great....10:38
gwhaleytrying to fathom who is dropping log entries and where - trying to see if there is a difference between if we log to a file and what ends up in journald10:39
jodhgwhaley: the --log= should work for the runtime, yes. The complication is passing that to the runtime with docker. The easiest method is to configure docker to call kata-runtime.sh and then do the --log= magic in there.10:39
gwhaleyright - I did consider using the 'via a shell script' trick ;-) I may have to go that route. Setting it in the docker daemon.json doesn't seem to be working for me10:40
jodhgwhaley: ... but, no, you can't currently create separate logs I don't think. We could do this, but it's a bit gross as I think we'd need to look at a magic envvar in config.json.10:40
gwhaleyOK, I'll go shell route. The docker docs say there is a 'runtimeArgs' json var you can set to pass args to a specific runtime, but I'm not seeing a log file appear. np10:41
*** djinni has quit IRC10:42
*** zerocoolback has quit IRC10:44
*** dlw has quit IRC10:44
*** LinuxMe has joined #kata-dev10:44
*** zerocoolback has joined #kata-dev10:46
*** LinuxMe has quit IRC10:48
*** jugs has quit IRC10:51
*** jugs has joined #kata-dev10:53
*** djinni has joined #kata-dev10:54
*** zerocoolback has quit IRC11:01
*** zerocoolback has joined #kata-dev11:06
*** gwhaley has quit IRC11:07
*** LinuxMe has joined #kata-dev11:09
*** LinuxMe_ has joined #kata-dev11:10
*** LinuxMe has quit IRC11:14
*** zerocoolback has quit IRC11:15
*** LinuxMe_ has quit IRC11:15
*** zerocoolback has joined #kata-dev11:16
stefanhaFor the record, the issue with a Fedora guest was that agent mis-detects the VMware vsock driver instead of using the virtio-serial port.11:18
stefanhaI or lsm5 will need to revisit this issue for Fedora.11:18
*** zerocoolback has quit IRC11:47
*** zerocoolback has joined #kata-dev11:49
*** devimc has joined #kata-dev11:51
*** LinuxMe has joined #kata-dev12:02
*** LinuxMe has quit IRC12:06
*** zerocoolback has quit IRC12:18
*** zerocoolback has joined #kata-dev12:18
lsm5stefanha: no changes to rootfs yet from my side, atm working on setting up a COPR repo with my spec file changes12:29
*** gwhaley has joined #kata-dev12:35
*** LinuxMe has joined #kata-dev12:38
*** LinuxMe has quit IRC12:43
*** fuentess has joined #kata-dev12:52
*** LinuxMe has joined #kata-dev13:02
stefanhalsm5: FWIW I just got Kata running on Fedora using a Fedora 28 rootfs.13:03
*** LinuxMe has quit IRC13:03
stefanhaIt's a generic, modular kernel, not a ClearContainers kernel.13:03
stefanhalsm5: I'll send you an email with details on the various things I needed to tweak.13:03
stefanhalsm5: I'm just playing around with Kata, not trying to create RPM packages, in case you're wondering.13:05
stefanhalsm5: But I guess you have or will hit the same issues as me when running it,.13:06
lsm5stefanha: ack, thanks, i have currently setup https://copr.fedorainfracloud.org/coprs/lsm5/kata/builds/ ..but only managed to get qemu-lite to build in copr, weird issues with other packages though they build just fine on fedora koji13:12
lsm5retrying with srpms instead of git sources13:14
*** LinuxMe has joined #kata-dev13:16
*** LinuxMe has quit IRC13:17
*** LinuxMe has joined #kata-dev13:17
*** LinuxMe has quit IRC13:27
*** LinuxMe has joined #kata-dev13:31
*** lamego has joined #kata-dev13:31
*** annabelleB has joined #kata-dev14:41
*** zerocoolback has quit IRC14:54
*** sameo has quit IRC15:06
*** openstack has quit IRC15:22
*** openstack has joined #kata-dev15:22
*** ChanServ sets mode: +o openstack15:22
*** zerocoolback has joined #kata-dev15:36
*** zerocoolback has quit IRC15:37
*** zerocoolback has joined #kata-dev15:38
*** fiddletwix has quit IRC15:42
*** zerocoolback has quit IRC15:42
*** libregeekingkid[ has quit IRC16:09
*** justJanne has quit IRC16:09
*** mugsie has quit IRC16:09
*** fiddletwix has joined #kata-dev16:13
*** libregeekingkid[ has joined #kata-dev16:14
*** justJanne has joined #kata-dev16:14
*** mugsie has joined #kata-dev16:14
clarkbI had to explicitly insmod vhost_net on fedora 28 kernel as well16:14
clarkbthis wasn't necessary on ubuntu xenial16:14
*** libregeekingkid[ has quit IRC16:17
*** annabelleB has quit IRC16:44
*** libregeekingkid[ has joined #kata-dev17:00
*** jodh has quit IRC17:11
*** openstack has quit IRC17:11
*** openstack has joined #kata-dev17:12
*** ChanServ sets mode: +o openstack17:12
*** LinuxMe has quit IRC17:14
*** gwhaley has quit IRC17:30
*** LinuxMe_ has joined #kata-dev17:37
*** zerocoolback has joined #kata-dev17:40
*** david-lyle has joined #kata-dev17:53
*** dklyle has quit IRC17:56
*** dklyle has joined #kata-dev17:57
*** david-lyle has quit IRC17:58
*** annabelleB has joined #kata-dev17:59
*** zerocoolback has quit IRC18:28
*** zerocoolback has joined #kata-dev18:28
*** zerocoolback has quit IRC18:33
*** annabelleB has quit IRC19:01
*** annabelleB has joined #kata-dev19:04
*** annabelleB has quit IRC19:07
*** davidgiluk has quit IRC19:26
*** annabelleB has joined #kata-dev19:36
*** annabelleB has quit IRC19:41
*** LinuxMe_ has quit IRC19:44
*** cdent has quit IRC20:09
clarkbsalvador.fuentes: as an updated the node failure issue is related to ipv6 networking in vexxhost. mnaser is going to look at it20:35
clarkb*as an update20:36
*** devimc has quit IRC21:27
*** fuentess has quit IRC21:35
*** LinuxMe has joined #kata-dev21:38
*** LinuxMe has quit IRC21:42
*** lamego has left #kata-dev21:45
*** LinuxMe has joined #kata-dev21:56
*** fuentess has joined #kata-dev22:14
*** LinuxMe has quit IRC22:29
*** fuentess has quit IRC23:03
*** devimc has joined #kata-dev23:31
*** LinuxMe has joined #kata-dev23:36
*** LinuxMe has quit IRC23:41

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