| *** bpradipt has joined #kata-dev | 04:52 | |
| *** sameo has joined #kata-dev | 05:25 | |
| *** bpradipt_ has joined #kata-dev | 05:34 | |
| *** bpradipt has quit IRC | 05:37 | |
| *** jodh has joined #kata-dev | 06:32 | |
| *** bpradipt_ has quit IRC | 07:16 | |
| *** sgarzare has joined #kata-dev | 07:19 | |
| *** fgiudici has joined #kata-dev | 07:32 | |
| *** bpradipt has joined #kata-dev | 07:47 | |
| *** bpradipt has quit IRC | 07:48 | |
| *** bpradipt has joined #kata-dev | 07:50 | |
| *** sameo has quit IRC | 08:00 | |
| *** sameo has joined #kata-dev | 08:21 | |
| *** bpradipt_ has joined #kata-dev | 08:25 | |
| *** bpradipt has quit IRC | 08:27 | |
| *** bpradipt_ has quit IRC | 08:35 | |
| *** sgarzare has quit IRC | 08:49 | |
| *** sgarzare_ has joined #kata-dev | 08:49 | |
| *** hashar has joined #kata-dev | 08:53 | |
| *** bpradipt has joined #kata-dev | 08:58 | |
| *** bpradipt has quit IRC | 09:20 | |
| *** bpradipt has joined #kata-dev | 10:00 | |
| *** fgiudici has quit IRC | 10:48 | |
| *** sgarzare has joined #kata-dev | 11:14 | |
| *** sgarzare_ has quit IRC | 11:15 | |
| *** fgiudici has joined #kata-dev | 12:18 | |
| *** bpradipt has quit IRC | 12:36 | |
| *** devimc has joined #kata-dev | 12:54 | |
| *** bpradipt has joined #kata-dev | 13:02 | |
| *** devimc has quit IRC | 13:07 | |
| *** sgarzare_ has joined #kata-dev | 13:14 | |
| *** sgarzare has quit IRC | 13:16 | |
| *** devimc has joined #kata-dev | 13:25 | |
| *** sgarzare__ has joined #kata-dev | 13:25 | |
| *** sgarzare_ has quit IRC | 13:28 | |
| *** sgarzare has joined #kata-dev | 13:51 | |
| *** sgarzare__ has quit IRC | 13:53 | |
| *** crobinso has joined #kata-dev | 13:57 | |
| *** devimc has quit IRC | 14:00 | |
| *** devimc has joined #kata-dev | 14:01 | |
| *** dklyle has joined #kata-dev | 14:10 | |
| *** sgarzare_ has joined #kata-dev | 14:45 | |
| *** sgarzare has quit IRC | 14:45 | |
| *** sgarzare_ has quit IRC | 14:47 | |
| *** sgarzare_ has joined #kata-dev | 14:47 | |
| *** hashar has quit IRC | 15:06 | |
| *** fgiudici_ has joined #kata-dev | 15:27 | |
| *** fgiudici has quit IRC | 15:28 | |
| *** bpradipt has quit IRC | 15:40 | |
| *** bpradipt has joined #kata-dev | 15:47 | |
| *** hashar has joined #kata-dev | 15:52 | |
| *** sgarzare_ has quit IRC | 15:53 | |
| *** fgiudici_ has quit IRC | 16:25 | |
| *** jodh has quit IRC | 17:02 | |
| kata-irc-bot | <archana.m.shinde> @fidencio Let me take a look at that | 17:14 |
|---|---|---|
| kata-irc-bot | <archana.m.shinde> I am trying to follow up on the simv2 gaps that we have with crio this week | 17:14 |
| kata-irc-bot | <fidencio> Sure! | 17:15 |
| kata-irc-bot | <archana.m.shinde> @fidencio I see you raised this PR: https://github.com/cri-o/cri-o/pull/3924/commits/a05b3dd1b8ec70230cdfcef7a27cfad462b55234 | 17:17 |
| kata-irc-bot | <fidencio> Yep, that should fix the issue reported by @rlk about the shimv2 + crio leaving processes behind | 17:20 |
| kata-irc-bot | <fidencio> Mind tho that my main focus is close the gaps with 1.x branches | 17:21 |
| kata-irc-bot | <fidencio> As using 2.x is out of question for us | 17:21 |
| kata-irc-bot | <fidencio> At least for now :slightly_smiling_face: | 17:21 |
| *** hashar has quit IRC | 17:22 | |
| kata-irc-bot | <archana.m.shinde> sure makes sense | 17:40 |
| kata-irc-bot | <saini.paramdeep> Hi All, I have a question on kata containers. I am running Kata containers in priv mode. When I m trying to set sysrq-trigger using echo b > /proc/sysrq-trigger, pod becomes unresponsive but kubernetes still shows it is in running mode. Is there a way to restart Kata VM from inside the kata containers. I have a requirement to reset the kata pod from kata container on certain situations. | 19:06 |
| devimc | @saini.paramdeep no, that's not possible | 19:19 |
| kata-irc-bot | <saini.paramdeep> @julio.montes thanks for the reply. It seems at this moment it is not possible. What I found Kata VM is unreachable after setting the trigger. We need a mechanism to inform kubernetes that Kata pod or VM is down and it should reset the env. However, I also observed that if Kata VM is down but not restarted. | 19:23 |
| *** bpradipt has quit IRC | 19:37 | |
| devimc | @saini.paramdeep what do you mean with "down"? is QEMU running ? | 19:37 |
| kata-irc-bot | <saini.paramdeep> Yes, Qemu is running but Kata VM is unreachable | 19:56 |
| *** crobinso has quit IRC | 20:14 | |
| *** sameo has quit IRC | 20:25 | |
| devimc | @saini.paramdeep ok, then we need a "keep alive" mechanism | 20:35 |
| kata-irc-bot | <archana.m.shinde> @fidencio We have been using the Redhat maintained repo for virtiofs so far: https://gitlab.com/virtio-fs/qemu/-/commits/virtio-fs/ | 20:37 |
| kata-irc-bot | <archana.m.shinde> Looks like qemu 5.0 has virtiofsd changes, was thinking to switch to qemu 5.0 for virtiofs support since we have already switched to that version with 9p | 20:39 |
| kata-irc-bot | <archana.m.shinde> question: are there any outstanding changes in the RH branch that are not part of qemu 5.0? | 20:40 |
| kata-irc-bot | <archana.m.shinde> @fidencio ^ | 20:41 |
| kata-irc-bot | <saini.paramdeep> @archana.m.shinde I have a stateful app and there are situations when we need to reset the VM to avoid data corruption. | 20:46 |
| kata-irc-bot | <saini.paramdeep> I do understand there is more work required to address this. As of now enabled sysrq triger in Guest VM kernel and I am not sure why resetting the sysrq will not restart the VM but it makes it unreachable. | 20:47 |
| *** th0din_ has joined #kata-dev | 20:48 | |
| *** th0din has quit IRC | 20:48 | |
| *** Yarboa has quit IRC | 20:51 | |
| *** hashar has joined #kata-dev | 20:54 | |
| *** sameo has joined #kata-dev | 21:08 | |
| *** devimc has quit IRC | 21:11 | |
| *** sameo has quit IRC | 21:14 | |
| *** crobinso has joined #kata-dev | 22:24 | |
| *** Yarboa has joined #kata-dev | 23:45 | |
| *** hashar has quit IRC | 23:56 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!