Thursday, 2019-09-12

*** igordc has quit IRC00:23
*** pcaruana has quit IRC01:09
*** dklyle has quit IRC01:42
*** david-lyle has joined #kata-dev01:42
*** david-lyle has quit IRC01:46
*** dklyle has joined #kata-dev01:47
*** pcaruana has joined #kata-dev04:32
*** pcaruana has quit IRC04:58
*** pcaruana has joined #kata-dev06:08
*** sameo has joined #kata-dev06:25
*** pcaruana has quit IRC06:41
*** sameo has quit IRC06:52
*** sgarzare has joined #kata-dev07:06
*** pcaruana has joined #kata-dev07:11
*** jodh has joined #kata-dev07:27
*** sameo has joined #kata-dev07:33
*** davidgiluk has joined #kata-dev07:58
*** sameo has quit IRC08:42
*** sameo has joined #kata-dev08:55
*** lpetrut has joined #kata-dev09:16
*** lpetrut has quit IRC09:23
*** lpetrut has joined #kata-dev09:24
*** lpetrut has quit IRC10:17
*** lpetrut has joined #kata-dev10:19
kata-irc-bot<niteshkonkar007> Hello All,  Is NVDIMM support necessary in qemu for virtio-fs + kata to work ? I could see "nvdimm" in the qemu command line here: https://github.com/kata-containers/documentation/blob/master/how-to/how-to-use-virtio-fs-with-kata.md Also is `qemu-system-x86_64_virt` == `nemu` coz the article talks about nemu support with kata?10:27
davidgilukniteshkonkar007: nemu is/was a cut down fork of qemu, the current qemu should be fine10:29
davidgilukniteshkonkar007: and nvdimm shouldn't be needed for virtiofs10:29
kata-irc-bot<niteshkonkar007> @davidgiluk: Thanks for the info. Before trying out virtio-fs with kata, I was trying it with just qemu following the instructions here: https://virtio-fs.gitlab.io/howto-qemu.html on ppc64le arch. Did not work out of the box. Was wondering if it was because of non-x86 arch or is a generic bug or I am missing something. https://www.redhat.com/archives/virtio-fs/2019-September/msg00115.html10:35
davidgilukniteshkonkar007: Yes I saw that but didn't have a chance to respond;  that was a known qemu build bug on newer compilers that's fixed in newer qemu/virtiofs tags10:36
davidgilukniteshkonkar007: Just try configuring with -Wno-error=format-tranncation should probably work around that (It's actually safe, it's just gcc doesn't realise that)10:37
kata-irc-bot<niteshkonkar007> @davidgiluk: I could build without any errors once I moved to `virtio-fs-v0.3` tag.10:43
davidgilukniteshkonkar007: Great, yes that usb problem was where a newer gcc introduced a new warning, then qemu played catchup to make it happy10:44
kata-irc-bot<niteshkonkar007> @davidgiluk: Cool. Now I will go ahead and try the remaning steps.10:47
*** sameo has quit IRC10:55
kata-irc-bot<jan.schintag> Hello All, i encountered an issue on s390x when starting 2 Containers on the Host. The second qemu cannot get a write lock on the image file, as the first qemu instance already has this. How is this solved on other architectures?11:36
*** sameo has joined #kata-dev12:05
*** fuentess has joined #kata-dev12:36
*** pcaruana has quit IRC13:30
*** devimc has joined #kata-dev13:55
*** pcaruana has joined #kata-dev14:08
*** pcaruana has quit IRC14:57
*** sameo has quit IRC15:09
*** lpetrut has quit IRC15:25
*** kgz has quit IRC16:31
*** kgz has joined #kata-dev16:45
*** sgarzare has quit IRC16:45
*** igordc has joined #kata-dev16:46
kata-irc-bot<eric.ernst> @archana.m.shinde around?17:00
kata-irc-bot<archana.m.shinde> @eric.ernst yup17:01
*** jodh has quit IRC17:04
*** pcaruana has joined #kata-dev17:58
*** devimc has quit IRC18:08
*** devimc has joined #kata-dev18:08
*** davidgiluk has quit IRC19:18
*** lpetrut has joined #kata-dev20:30
*** pcaruana has quit IRC20:32
*** fuentess has quit IRC20:35
*** fuentess has joined #kata-dev20:40
*** lpetrut has quit IRC20:46
*** devimc has quit IRC21:42
*** igordc has quit IRC23:34

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