Monday, 2019-07-29

*** igordc has quit IRC01:24
*** gmmaha has quit IRC04:41
*** gmmaha has joined #kata-dev04:51
*** sameo has joined #kata-dev05:15
*** brtknr has quit IRC05:17
*** brtknr has joined #kata-dev05:19
*** sameo has quit IRC05:25
*** jasonyangdaisy has joined #kata-dev06:30
*** jasonyangdaisy has quit IRC06:44
*** jodh has joined #kata-dev06:50
*** sgarzare has joined #kata-dev07:09
*** pcaruana has joined #kata-dev07:31
*** lpetrut has joined #kata-dev07:51
*** davidgiluk has joined #kata-dev08:02
*** gwhaley has joined #kata-dev08:11
kata-irc-bot<alessandro.randazzo> quick question : I'm following the documentation guide and I has arrived  at : sudo kata-runtime kata-check and I'm getting the error : file /usr/share/kata-containers/vmlinuz.container does not exist . Should I jump on https://github.com/kata-containers/packaging/tree/master/kernel#build-kata-containers-kernel and follow the instructions? Thanks (My environment is based on a lubuntu vm running in vmware workstation with08:18
kata-irc-botenabled nested virtualization) (edited)08:18
*** brtknr has quit IRC08:33
*** brtknr has joined #kata-dev08:35
*** lpetrut has quit IRC08:58
kata-irc-bot<graham.whaley> @alessandro.randazzo - *exactly* which document are you following - as that will determine what/how that binary should have been installed... please point us to the exact document you used, and then we can try and figure out if there is a documentation flow error or if something has actually gone wrong etc.09:13
*** altlogbot_3 has quit IRC09:24
*** altlogbot_2 has joined #kata-dev09:24
kata-irc-bot<alessandro.randazzo> @graham.whaley I've started from the beginning of this : https://github.com/kata-containers/documentation/blob/master/Developer-Guide.md#requirements-to-build-individual-components . I firstly checked the requirements to build individual components , then build and install kata containers runtime, then after running 'check hardware requirements' I got the above error.09:46
kata-irc-bot<graham.whaley> Ah, thanks @alessandro.randazzo - then, yes indeed, I think you will need to build and install the other components required by the runtime (the kernel image and rootfs image).09:54
kata-irc-bot<alessandro.randazzo> I've installed  the latest stable version of golang...I will let you know if it can generate some trouble instead of using the recommended one.10:08
*** jugs has quit IRC10:28
*** jugs has joined #kata-dev10:28
*** brtknr has quit IRC10:30
*** brtknr has joined #kata-dev10:32
*** brtknr has quit IRC10:34
*** brtknr has joined #kata-dev10:35
*** brtknr has quit IRC10:36
*** brtknr has joined #kata-dev10:45
*** brtknr has quit IRC11:04
*** brtknr has joined #kata-dev11:05
*** brtknr has quit IRC11:06
*** brtknr has joined #kata-dev11:06
*** brtknr has quit IRC11:07
*** lpetrut has joined #kata-dev11:07
*** brtknr has joined #kata-dev11:08
*** gwhaley has quit IRC11:12
*** brtknr has quit IRC11:20
*** brtknr has joined #kata-dev11:21
*** brtknr has quit IRC11:22
*** brtknr has joined #kata-dev11:23
*** brtknr has quit IRC11:23
*** brtknr has joined #kata-dev11:24
*** brtknr has quit IRC11:24
*** brtknr has joined #kata-dev11:25
*** gwhaley has joined #kata-dev11:57
*** fuentess has joined #kata-dev12:40
*** devimc has joined #kata-dev13:08
*** dklyle has quit IRC14:00
*** dklyle has joined #kata-dev14:00
*** gmmaha has quit IRC14:09
*** gmmaha has joined #kata-dev14:13
*** devimc has quit IRC14:14
*** devimc has joined #kata-dev14:15
*** lpetrut has quit IRC14:39
stefanhaIs Kata moving to a newer kernel in the next release?  virtio-fs has gotten a number of bug fixes that we'd like to make available in Kata, so I wanted to check which kernel version we should target.14:42
gwhaleystefanha: we discussed this last week or so I think whilst we were pushing throught the kernel fragments PR - iirc, the decision is to stay on latest longterm, hence still 4.19.x right now.14:49
stefanhagwhaley: Thank you!  We're keen to be on a recent kernel version but I understand Kata wants a long-term/stable kernel.14:52
gwhaleystefanha: it is a constant debate we have - we keep itching to move to 5.x, but we have to decide between longterm/stable/HEAD-ish..... and currently longterm wins ;-)14:56
stefanhagwhaley: I think the virtio-fs strategy will be to treat Kata's kernel as a stable branch - only backport critical fixes.  If it's a recent kernel we could backport the latest upstream code (easier to do and potentially has better performance and features).15:05
stefanhagwhaley: They have pros and cons, but it sounds like treating it as a stable branch is the right fit.15:05
gwhaley^^ /cc @gmmaha @eernst just fyi.15:11
devimcgwhaley, stefanha,  +1  - I'd like to support PVH (raw kernel)15:30
*** aleofuu38 has joined #kata-dev15:33
gmmahagwhaley: stefanha: thanks.. yes, we are staying on 4.19.x for now.15:50
gmmahawill see how soon we can move to 5.x given there are others who would like that change...15:50
gmmahanow that we have fragments in place (thanks to devimc) we should think about hoow upgrades would work for us.15:50
devimcgmmaha, and thanks to gwhaley ^^15:52
devimcgmmaha, the current fragments don't work with 5.x, a lot of option were removed15:53
devimcor renamed15:53
gwhaleydevimc, gmmaha: oh, the pain :-( Yeah, one of the next steps with the fragments (which I had originally, but removed as @Eric was hoping we could do without it ... but, it turns out we probably cannot....) is to support kernel version specific fragments :-(15:55
aleofuu38I got stuck in building the kata-kernel...may I past the error in here?16:06
gwhaleyaleofuu38: sure you can - if it gets too complex, then maybe we open a github issue. I presume you are using the instructions from https://github.com/kata-containers/packaging/tree/master/kernel and using build-kernel.sh16:07
gwhaley^^ @jcvenega16:08
aleofuu38gwhaley yes, I locally downloaded all stuff from https://github.com/kata-containers/packaging and followed the instructions ...below the error : INFO: Clone config and patchesINFO: Config version: 47INFO: Kernel version: 4.19.52  LEX     scripts/kconfig/zconf.lex.c  HOSTCC  scripts/kconfig/zconf.tab.o  HOSTLD  scripts/kconfig/confscripts/kconfig/co16:15
aleofuu38nf  --syncconfig Kconfig****** Configuration file ".config" not found!****** Please run some configurator (e.g. "make oldconfig" or*** "make menuconfig" or "make xconfig").***make[2]: *** [scripts/kconfig/Makefile:69: syncconfig] Error 1make[1]: *** [Makefile:532: syncconfig] Error 2make: *** [Makefile:631: include/config/auto.conf.cmd] Error 216:15
aleofuu38should I try "make oldconfig" ?16:17
gwhaleyaleofuu38: did you run the build-kernel.sh setup first - like on https://github.com/kata-containers/packaging/tree/master/kernel#setup-kernel-source-code - as that should generate/copy the .config file into the kernel source tree before it tries to build it16:18
aleofuu38yes I did16:19
aleofuu38Do I try re-running it?16:20
gwhaleyhmm, OK - two suggestions then - you could run 'bash -x ./build-kernel.sh setup' and check what it is doing... or, you can open a github Issue and add details of what you ran, and what your system is :-)16:20
gwhaleyaleofuu38: I think you can re-run it - it may complain the source tree already exists though. so, you may need to rm the untar'd kernel source subdir and re-run. iirc, it will spot you have already downloaded the kernel tarball, and not pull that again, just untar it...16:21
aleofuu38thus, under kernel folder should I remove everything except linux-4.19.52.tar.xz ?16:24
gwhaleyno - iirc, there is a subdir created (I don't have a 'used' tree to look at right now), that contains all the kernel source - that is the dir to remove. So, do not remove build-kernel.sh, configs, kata_config_version, patches or the README - there should be another dir though that you need to remove... maybe 'linux-4.19.38' or similar... /me guesses at name now...16:27
*** devimc has quit IRC16:29
gwhaleyaleofuu38: called something like 'kata-linux-<version>-<version>' I think, from trying to decode the script ;-)  In fact, if you run the script, it will probably complain that the dir already exists, and tell you its name..16:30
*** devimc has joined #kata-dev16:30
aleofuu38ok, under kernel dir there is another one ,named kata-linux-4.19.52-47. I guest is the only to be removed16:30
gwhaleyyep!16:30
aleofuu38(y)16:31
*** sgarzare has quit IRC16:53
aleofuu38after some other installation like libelf-dev , I re-run the kernel building process and seems everithing ok. Finale message is : Kernel: arch/x86/boot/bzImage is ready  (#1)16:55
aleofuu38sorry for typos :)16:56
gwhaleyaleofuu38: excellent. yes, you need iirc all the tools on the host you would normally need to do a kernel build... the only other option would be for us to set up a docker image with all the tools as an alternative (which we do do for the rootfs image build iirc)... glad it is working now ;-)16:56
*** igordc has joined #kata-dev16:59
aleofuu38now I can try installing the kernel and then can I re-run sudo kata-runtime kata-check  or after installed the kernel  I also need to create a rootfs image first?17:02
*** jodh has quit IRC17:02
gwhaleyaleofuu38: I suspect you will need a rootfs image as well. have a look in the osbuilder repo for that.17:02
* gwhaley signs off..17:02
*** gwhaley has quit IRC17:02
*** eernst_ has joined #kata-dev17:26
*** eernst_ has quit IRC17:28
*** eernst has joined #kata-dev17:28
*** devimc has quit IRC18:59
*** devimc has joined #kata-dev19:00
*** davidgiluk has quit IRC19:01
*** devimc has quit IRC19:15
*** devimc has joined #kata-dev19:15
*** aleofuu38 has quit IRC20:35
*** fuentess has quit IRC21:48
*** devimc has quit IRC22:06
*** eernst has quit IRC22:40

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