| kata-irc-bot | <efoster> So this is probably a dumb question. I'm in the process of switching from Kata 1.x to 2.x. I see the shim process start when I try to start a container, but qemu never launches, and I'm seeing this in the logs: ```level=error msg="Failed to connect to QEMU instance" error="dial unix /run/vc/vm/c7a221e16232c1a0a57a7df3700c0eeaa9ab2a7452954e645241d49084aac14f/qmp.sock: connect: connection refused" name=containerd-shim-v2 pid=889834 | 15:22 |
|---|---|---|
| kata-irc-bot | sandbox=c7a221e16232c1a0a57a7df3700c0eeaa9ab2a7452954e645241d49084aac14f source=virtcontainers subsystem=qemu``` When I try to run `/opt/kata/bin/qemu-system-x86_64`, I get this: ```vmss-agent-katastandard-test-npfsh000000 ~ # opt/kata/bin/qemu-system-x86_64 -bash: opt/kata/bin/qemu-system-x86_64: No such file or directory``` I've installed Kata using the static tarball included with 2.1.1 via `tar -xvf kata.tar.xz -C /`. Am I missing a | 15:22 |
| kata-irc-bot | prerequisite? | 15:22 |
| kata-irc-bot | <efoster> When I try to run that binary on my Linux workstation, I get the same error. | 15:23 |
| kata-irc-bot | <efoster> I also built `qemu-experimental` using `build-static-qemu-experimental.sh`, and I have the same issue there. | 15:24 |
| kata-irc-bot | <efoster> ```vmss-agent-katastandard-test-npfsh000000 tmp # find /opt/kata -name '*.bin' /opt/kata/share/kata-qemu/qemu/bios-microvm.bin /opt/kata/share/kata-qemu/qemu/pvh.bin /opt/kata/share/kata-qemu/qemu/linuxboot_dma.bin /opt/kata/share/kata-qemu/qemu/bios.bin /opt/kata/share/kata-qemu/qemu/bios-256k.bin /opt/kata/share/kata-qemu/qemu/kvmvapic.bin /opt/kata/share/kata-qemu/qemu/linuxboot.bin | 15:26 |
| kata-irc-bot | /opt/kata/share/kata-qemu-experimental/qemu/bios-microvm.bin /opt/kata/share/kata-qemu-experimental/qemu/pvh.bin /opt/kata/share/kata-qemu-experimental/qemu/linuxboot_dma.bin /opt/kata/share/kata-qemu-experimental/qemu/bios.bin /opt/kata/share/kata-qemu-experimental/qemu/bios-256k.bin /opt/kata/share/kata-qemu-experimental/qemu/kvmvapic.bin /opt/kata/share/kata-qemu-experimental/qemu/linuxboot.bin``` | 15:26 |
| kata-irc-bot | <efoster> Ooooh... wait a minute. I wonder if this is an upgrade- related problem. | 15:26 |
| kata-irc-bot | <efoster> I did a `mv /opt/kata /opt/kata-bak` before I untarred 2.x | 15:26 |
| kata-irc-bot | <efoster> but I'm guessing there may be something I'm missing | 15:26 |
| kata-irc-bot | <efoster> hmm, no | 15:28 |
| kata-irc-bot | <efoster> that wouldn't make sense | 15:28 |
| kata-irc-bot | <efoster> because things should still run correctly on my workstation | 15:28 |
| kata-irc-bot | <efoster> I've tried 2.1.1 and 2.1.0 | 15:28 |
| kata-irc-bot | <efoster> let me try 2.0.4 | 15:28 |
| kata-irc-bot | <efoster> because I swear I tried this with 2.x before and it worked... | 15:29 |
| kata-irc-bot | <efoster> Same deal with 2.0.4 | 15:32 |
| kata-irc-bot | <efoster> Am I losing my mind? I could have sworn this worked... | 15:49 |
| kata-irc-bot | <efoster> OK | 15:50 |
| kata-irc-bot | <efoster> I am clearly losing my mind. | 15:50 |
| kata-irc-bot | <efoster> chasing the wrong thing here. | 15:50 |
| kata-irc-bot | <efoster> `Property 'vhost-user-fs-pci.cache-size' not found` | 15:54 |
| kata-irc-bot | <efoster> Ohhh. | 15:56 |
| kata-irc-bot | <efoster> https://github.com/kata-containers/kata-containers/issues/1132 possibly? | 15:56 |
| devimc | @efoster are you using ctr to run kata? | 15:57 |
| devimc | static tarball should work, at least it works for me | 15:57 |
| kata-irc-bot | <efoster> Not in this case, no. Kubernetes is launching a pod through CRI-O | 15:58 |
| devimc | ok, take a look to the journal, maybe you can get something useful | 15:58 |
| devimc | journalctl -b -t kata | 15:58 |
| devimc | is kata running in a VM (nested virtualization) ? | 15:59 |
| kata-irc-bot | <efoster> Aha! All I had to do was configure it to use `qemu-system-x86_64-experimental`. I'm guessing the featureset I'm using isn't supported by the version of QEMU shipped in the tarball. | 15:59 |
| devimc | maybe | 16:00 |
| kata-irc-bot | <efoster> Let me share my config in a gist | 16:01 |
| kata-irc-bot | <efoster> https://gist.github.com/evanfoster/b528ac672324d79bab514c3ed48ededf There's a weirdo config option in there because I was testing https://github.com/kata-containers/kata-containers/issues/2053 | 16:03 |
| kata-irc-bot | <eric.adams> I am also having issues getting Kata to work with containerd and I am not sure what I did wrong since I've set this up many times in the past. My kubeadm versions are newer than in the past since Kubespray updated. It works if I use the `ctr` command posted above but something is not configured correctly in my Kubernetes setup. Whenever I try to run a Kata container in Kubernetes I get `Failed to create pod sandbox: rpc error: | 18:14 |
| kata-irc-bot | code = Unknown desc = failed to create containerd task: the file /pause is not exist: unknown` | 18:14 |
| kata-irc-bot | <eric.ernst> ctr version, @eric.adams? | 21:02 |
| kata-irc-bot | <eric.adams> @eric.ernst It is 1.4.6. I am wondering if this particular issue I am having is the Docker rate limiting issue. | 21:24 |
| kata-irc-bot | <eric.adams> I switched to crio to keep testing. I'll try containerd again later. | 21:24 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!