| *** eernst_ has quit IRC | 01:19 | |
| *** igordc has quit IRC | 01:31 | |
| *** eernst has joined #kata-dev | 01:50 | |
| *** eernst has quit IRC | 01:58 | |
| *** eernst has joined #kata-dev | 03:05 | |
| *** sameo has joined #kata-dev | 04:10 | |
| *** sameo has quit IRC | 04:44 | |
| *** eernst has quit IRC | 04:55 | |
| *** sameo has joined #kata-dev | 05:16 | |
| *** sameo has quit IRC | 05:26 | |
| *** jugs has quit IRC | 05:58 | |
| *** jugs has joined #kata-dev | 05:58 | |
| *** pcaruana has quit IRC | 07:12 | |
| *** sgarzare has joined #kata-dev | 07:18 | |
| *** jodh has joined #kata-dev | 07:27 | |
| *** pcaruana has joined #kata-dev | 07:42 | |
| *** gwhaley has joined #kata-dev | 08:00 | |
| *** davidgiluk has joined #kata-dev | 08:02 | |
| *** lpetrut has joined #kata-dev | 08:03 | |
| *** lpetrut has quit IRC | 08:04 | |
| *** lpetrut has joined #kata-dev | 08:04 | |
| *** lpetrut has quit IRC | 08:29 | |
| kata-irc-bot | <alessandro.randazzo> Hi All, I created rootfs based on Alpine distribution yesterday and I can see the fs under 'kata-containers/osbuilder/rootfs-builder/rootfs-Alpine' (I got this result by typing: 'sudo -E PATH=$PATH ./rootfs.sh alpine'. Today, I run 'sudo kata-runtime kata-check' and I still have the error that can't find an image or initrd . I, then, run 'sudo ./image_builder.sh | 08:51 |
|---|---|---|
| kata-irc-bot | /home/alex/goprojects/src/github.com/kata-containers/osbuilder/rootfs-builder/rootfs-Alpine' and I got : '[OK] init is installed ERROR: /lib/systemd/systemd is not installed in /home/alex/goprojects/src/github.com/kata-containers/osbuilder/rootfs-builder/rootfs-Alpine ERROR: Invalid rootfs' . This happens , i guess, cause Alpine is not based on systemd. I read that I should specify AGENT_INIT=yes . Thus, my question is : Do I need to re-create | 08:51 |
| kata-irc-bot | rootfs by specifying 'sudo -E PATH=$PATH AGENT_INIT=yes ./rootfs.sh alpine' and later run : 'sudo ./image_builder.sh /path/to/rootfs' ? or Could I simply re-run 'sudo ./image_builder.sh /path/to/rootfs' by adding the flag AGENT_INIT=yes? | 08:51 |
| kata-irc-bot | <alessandro.randazzo> Ok, I self-replied ..it was sufficient to re-run ''sudo AGENT_INIT=yes' ./image_builder.sh /path/to/rootfs' | 09:02 |
| *** brtknr has joined #kata-dev | 09:22 | |
| *** sameo has joined #kata-dev | 09:58 | |
| *** sameo has quit IRC | 10:03 | |
| *** gwhaley has quit IRC | 11:23 | |
| *** jodh has quit IRC | 12:27 | |
| *** jodh has joined #kata-dev | 12:28 | |
| *** sameo has joined #kata-dev | 12:29 | |
| *** jodh has quit IRC | 12:30 | |
| *** gwhaley has joined #kata-dev | 12:32 | |
| *** fuentess has joined #kata-dev | 12:32 | |
| *** jodh has joined #kata-dev | 12:54 | |
| *** devimc has joined #kata-dev | 13:08 | |
| kata-irc-bot | <alessandro.randazzo> I guess next step is: installing kata-proxy :slightly_smiling_face: ...below the message after typing 'sudo kata-runtime kata-check' INFO[0000] loaded configuration file=/usr/share/defaults/kata-containers/configuration-qemu.toml format=TOML ERRO[0000] file /usr/libexec/kata-containers/kata-proxy does not exist arch=amd64 name=kata-runtime pid=3697 source=runtime file | 13:47 |
| kata-irc-bot | /usr/libexec/kata-containers/kata-proxy does not exist . Correct? | 13:47 |
| kata-irc-bot | <graham.whaley> @alessandro.randazzo yes, kata-proxy and kata-shim both. I think one of them might be optional depending on your system setup (use of vsock etc.), but I always forget which - they are both tiny, so just build/install both ;) | 13:55 |
| kata-irc-bot | <alessandro.randazzo> thanks @graham.whaley already done...I think I finished to install anything except......please see my latest output by kata-check : | 13:59 |
| kata-irc-bot | <alessandro.randazzo> WARN[0000] modprobe insert module failed: modprobe: ERROR: could not insert 'vhost_vsock': Device or resource busy arch=amd64 error="exit status 1" module=vhost_vsock name=kata-runtime pid=5666 source=runtime ERRO[0000] kernel property not found arch=amd64 description="Host Support for Linux VM Sockets" name=vhost_vsock pid=5666 source=runtime type=module | 13:59 |
| kata-irc-bot | <alessandro.randazzo> everything is fine except a warning and one error | 13:59 |
| kata-irc-bot | <graham.whaley> the vhost vsock warning I'm pretty sure you will be OK with - just means you maybe cannot use vsock mode for Kata (vsock mode is the more efficient 'modern' way though). As for the error - I think that is saying the same thing... yeah, sometimes it is hard to tell from kata check what is fatal and what is not I think. /cc @james.o.hunt | 14:01 |
| kata-irc-bot | <alessandro.randazzo> reason why I can't use vhost what does it depend on? Maybe because my host is a virtual machine? | 14:02 |
| kata-irc-bot | <graham.whaley> kernel version and distro I suspect - if your kernel is too old to have the feature (pre 4.15 maybe iirc), or does not have the module installed (maybe it is not part of that distro of is an extra package), then the feature will not be available. | 14:03 |
| kata-irc-bot | <alessandro.randazzo> my kernel is 5.0.0-21-generic | 14:04 |
| kata-irc-bot | <alessandro.randazzo> while I'll be waiting for ...I try to figure out if I can turn vsock on :slightly_smiling_face: | 14:06 |
| kata-irc-bot | <alessandro.randazzo> question.... this warning refers to host's kernel or that of my guest | 14:09 |
| kata-irc-bot | <james.o.hunt> @graham.whaley there have been changes to the check command. Can't find the PR refs atm but there are quite a few scenarios it has to deal with. Maybe we could do (slightly) better but whatever we do, someone gets upset with the result ;) | 14:10 |
| kata-irc-bot | <james.o.hunt> @alessandro.randazzo - that's a host kernel issue | 14:10 |
| kata-irc-bot | <alessandro.randazzo> any tip to fix it? | 14:11 |
| kata-irc-bot | <james.o.hunt> if you're running on an old distro like centos 5, you may not have the feature. | 14:11 |
| kata-irc-bot | <alessandro.randazzo> it's Lubuntu 19. | 14:11 |
| kata-irc-bot | <james.o.hunt> sorry, no idea in that case ;) | 14:11 |
| kata-irc-bot | <james.o.hunt> is that new? | 14:11 |
| kata-irc-bot | <alessandro.randazzo> yes indeed | 14:12 |
| kata-irc-bot | <alessandro.randazzo> Ubuntu 19.04 \n \l | 14:13 |
| kata-irc-bot | <alessandro.randazzo> above what I get by cat /etc/issue | 14:13 |
| kata-irc-bot | <graham.whaley> @alessandro.randazzo - the test/check has basically tried to `insmod` or `modprobe` and/or `lsmod` for the kernel `vhost_vsock` feature, and failed. Sooo, you can chase that down and try that by hand to figure out why - be that a missing feature (not compiled into the kernel) or a missing module (not installed in the filesystem) etc.... | 14:15 |
| kata-irc-bot | <alessandro.randazzo> ok that's clear :slightly_smiling_face: I'm going to investigate more | 14:16 |
| kata-irc-bot | <james.o.hunt> @alessandro.randazzo - I have seen issues with that module where it seems to get "entangled" with other modules. I tend to load it straight after boot. Try this: | 14:17 |
| kata-irc-bot | <james.o.hunt> `sudo modprobe -r vmw_vsock_virtio_transport_common && sudo modprobe -r vmw_vsock_virtio_transport && sudo modprobe -r vhost_net && sudo modprobe -r vhost` | 14:17 |
| kata-irc-bot | <james.o.hunt> Then, `sudo moprobe vhost_sock && sudo modprobe vhost_net` | 14:18 |
| kata-irc-bot | <alessandro.randazzo> :+1: thanks I'm trying | 14:18 |
| *** devimc has quit IRC | 14:19 | |
| *** devimc has joined #kata-dev | 14:20 | |
| kata-irc-bot | <alessandro.randazzo> ok, running the first returns the input mode without any error or message, then I run the second and says : Module vhost_sock not found in directory /lib/modules/5.0.0-21-generic . At this point Do I need to rebuild the host kernel and adding the missing module? | 14:21 |
| devimc | I think so, you need vsocks support in both host and guest | 14:22 |
| kata-irc-bot | <graham.whaley> see if Lubuntu supplies it in a package - might be a 'module extras' or something. And also you could check the lubuntu kernel config (you might be able to find the file in /proc with them in) to see if vsock/virtio is enabled in the lubuntu kernel at all. | 14:22 |
| kata-irc-bot | <alessandro.randazzo> :+1: | 14:23 |
| kata-irc-bot | <alessandro.randazzo> Just to be sure the only modules that I need to load are only : vmw_vsock_virtio_transport_common vmw_vsock_virtio_transport vhost_net vhost | 15:00 |
| kata-irc-bot | <graham.whaley> aha, and there might be the issue - those `vmw` ones are the *vmware* drivers I believe - and you cannot mix the vmware ones with the KVM (that kata uses) ones at the same time (let's call it a design limitation...). | 15:01 |
| kata-irc-bot | <graham.whaley> let me see, I have a feeling there is an Issue or something in our repos somewhere that talks about unloading the vmware ones first.. | 15:01 |
| kata-irc-bot | <graham.whaley> or, maybe that 'vmw' is misleading me - there are only two mentions in the github repos, and the code one in the agent makes it look like that is a valid device... https://github.com/kata-containers/agent/blob/4f462c54391db11e7d1bc73153eb460996d74a2a/channel.go#L271-L276 /cc @julio.montes @stefanha - are you able to clarify? | 15:04 |
| kata-irc-bot | <alessandro.randazzo> in the meantime, I can try installing vhost_net and vhost that seem not to related to vmware | 15:10 |
| kata-irc-bot | <alessandro.randazzo> cat modules | grep vsock --- > output vmw_vsock_vmci_transport 32768 2 - Live 0x0000000000000000 vsock 36864 3 vmw_vsock_vmci_transport, Live 0x0000000000000000 vmw_vmci 69632 2 vmw_vsock_vmci_transport,vmw_balloon, Live 0x0000000000000000 | 15:10 |
| kata-irc-bot | <alessandro.randazzo> at modules | grep vmw -----> output vmw_vsock_vmci_transport 32768 2 - Live 0x0000000000000000 vsock 36864 3 vmw_vsock_vmci_transport, Live 0x0000000000000000 vmw_balloon 24576 0 - Live 0x0000000000000000 vmw_vmci 69632 2 vmw_vsock_vmci_transport,vmw_balloon, Live 0x0000000000000000 vmwgfx 290816 8 - Live 0x0000000000000000 ttm 102400 1 vmwgfx, Live 0x0000000000000000 drm_kms_helper 180224 1 vmwgfx, Live 0x0000000000000000 | 15:12 |
| kata-irc-bot | drm 475136 11 vmwgfx,ttm,drm_kms_helper, Live 0x0000000000000000 | 15:12 |
| devimc | gwhaley, Archana added this | 15:18 |
| kata-irc-bot | <alessandro.randazzo> I just had a look at /lib/modules/5.0.0-21-generic/kernel/net/vmw_vsock please see the picture | 15:35 |
| kata-irc-bot | <alessandro.randazzo> as far as I understand, since I'm working on a VMware VM these modules are already hooked up with VMware that's why kata-check complains.... could it be? | 15:38 |
| kata-irc-bot | <graham.whaley> @alessandro.randazzo - aha, I think I found the doc ... we may have it written down (just, well, in the architecture part of vsock docs in kata...) Have a peek at: https://github.com/kata-containers/documentation/blob/master/design/VSocks.md#with-vmware-guest | 15:40 |
| kata-irc-bot | <alessandro.randazzo> cool! great @graham.whaley you saved a potential headache :slightly_smiling_face: ...I run kata-check and everything is fine now even though I lost drag and drop and cut and post utilities :,) | 15:48 |
| *** igordc has joined #kata-dev | 16:08 | |
| *** sgarzare has quit IRC | 16:49 | |
| *** gwhaley has quit IRC | 16:59 | |
| *** jodh has quit IRC | 17:00 | |
| *** igordc has quit IRC | 17:03 | |
| kata-irc-bot | <alessandro.randazzo> I would like to start playing a bit with kata-runtime, I can see the commands create/delete/stop etc.. if I want, for example, to run busybox image since I am not using any orchestrator, should I first download it via wget (for example) and then running 'kata-runtime create -b /path/to/Alpine-rootfs? ' Or for each container/service that I want to play with Do I need to create an OCI bundle? | 17:10 |
| kata-irc-bot | <eric.ernst> Around @graham.whaley ? | 17:23 |
| *** igordc has joined #kata-dev | 17:27 | |
| *** igordc has quit IRC | 17:30 | |
| *** igordc has joined #kata-dev | 17:42 | |
| *** fuentess has quit IRC | 18:29 | |
| *** sameo has quit IRC | 18:59 | |
| *** davidgiluk has quit IRC | 19:15 | |
| *** eernst has joined #kata-dev | 19:25 | |
| *** fuentess has joined #kata-dev | 19:27 | |
| *** fuentess has quit IRC | 20:59 | |
| *** devimc has quit IRC | 21:28 | |
| *** eernst has quit IRC | 21:38 | |
| *** iamweswilson_ has joined #kata-dev | 22:29 | |
| *** iamweswilson has quit IRC | 22:37 | |
| *** iamweswilson_ is now known as iamweswilson | 22:37 | |
| *** igordc has quit IRC | 23:10 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!