| kata-irc-bot | <bergwolf> ```108 qemu-experimental: 109 description: "QEMU with virtiofs support" 110 url: "https://github.com/qemu/qemu" 111 version: "7a800cf9496fddddf71b21a00991e0ec757a170a"``` | 02:41 |
|---|---|---|
| kata-irc-bot | <bergwolf> It is in the qemu repo | 02:41 |
| kata-irc-bot | <bergwolf> plus the patches under tools/packaging/qemu/patches/tag_patches/7a800cf9496fddddf71b21a00991e0ec757a170a directory | 02:42 |
| kata-irc-bot | <bergwolf> ```0001-DAX-vhost-user-Rework-slave-return-values.patch 0010-DAX-virtiofsd-Add-setup-remove-mappings-fuse-command.patch 0019-DAX-unmap-virtiofsd-Route-unmappable-reads.patch 0002-DAX-libvhost-user-Route-slave-message-payload.patch 0011-DAX-virtiofsd-Add-setup-remove-mapping-handlers-to-p.patch 0020-DAX-unmap-virtiofsd-route-unmappable-write-to-slave-.patch | 02:42 |
| kata-irc-bot | 0003-DAX-libvhost-user-Allow-popping-a-queue-element-with.patch 0012-DAX-virtiofsd-Wire-up-passthrough_ll-s-lo_setupmappi.patch 0021-DAX-virtiofsd-implement-FUSE_INIT-map_alignment-fiel.patch 0004-DAX-subprojects-libvhost-user-Add-virtio-fs-slave-ty.patch 0013-DAX-virtiofsd-Make-lo_removemapping-work.patch 0022-vhost-user-fs-Extend-VhostUserFSSlaveMsg-to-pass-add.patch 0005-DAX-virtio-Add-shared-memory-capability.patch | 02:42 |
| kata-irc-bot | 0014-DAX-virtiofsd-route-se-down-to-destroy-method.patch 0023-vhost-user-fs-Implement-drop-CAP_FSETID-functionalit.patch 0006-DAX-virtio-fs-Add-cache-BAR.patch 0015-DAX-virtiofsd-Perform-an-unmap-on-destroy.patch 0024-virtiofsd-Ask-qemu-to-drop-CAP_FSETID-if-client-aske.patch 0007-DAX-virtio-fs-Add-vhost-user-slave-commands-for-mapp.patch | 02:42 |
| kata-irc-bot | 0016-DAX-unmap-virtiofsd-Add-VHOST_USER_SLAVE_FS_IO.patch 0025-virtiofsd-Add-printf-checking-to-fuse_log.patch 0008-DAX-virtio-fs-Fill-in-slave-commands-for-mapping.patch 0017-DAX-unmap-virtiofsd-Add-wrappers-for-VHOST_USER_SLAV.patch 0009-DAX-virtiofsd-Add-cache-accessor-functions.patch 0018-DAX-unmap-virtiofsd-Parse-unmappable-elements.patch``` | 02:42 |
| kata-irc-bot | <bergwolf> or you can use the static binaries in the release tarball. Use the one with `-virtiofs` suffix | 02:43 |
| kata-irc-bot | <shuo.chen> I believe the static binary in release tarball with the virtiofs suffix does not exists since some 2.x version. | 04:57 |
| kata-irc-bot | <bergwolf> @fidencio @eric.ernst do you remember why they (qemu virtiofs-DAX binaries) were dropped? | 06:15 |
| kata-irc-bot | <fidencio> @bergwolf because dax support was merged into QEMU, AFAIR | 07:19 |
| kata-irc-bot | <bergwolf> so we can drop the DAX patches in `tools/packaging/qemu/patches/tag_patches` ? | 07:20 |
| kata-irc-bot | <bergwolf> and @shuo.chen should try the latest qemu? Any version requirement suggestions? | 07:21 |
| kata-irc-bot | <shuo.chen> I am using the qemu from the upstream release artifacts. Can we get the newer qemu version in next release or so? | 07:42 |
| kata-irc-bot | <fidencio> That one should work | 07:44 |
| kata-irc-bot | <liubin0329> I think I have tried the 6.1.0 QEMU and get the same error like shuo chen. | 08:27 |
| kata-irc-bot | <fidencio> This may be a release blocker for 2.3.0, to be completely fair | 08:41 |
| kata-irc-bot | <fidencio> @shuo.chen, @liubin0329, can we see the full QEMU command line? | 08:53 |
| kata-irc-bot | <liubin0329> My qemu version ```$ /opt/kata/bin/qemu-system-x86_64 --version QEMU emulator version 6.1.0 (kata-static) Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers``` Start command ```Nov 23 16:54:56 kant-server containerd[12860]: time="2021-11-23T16:54:56.617425037+08:00" level=info msg="launching /opt/kata/bin/qemu-system-x86_64 with: [-name sandbox-977c24e8414012d8116847b57b4a32ced3c21e94de0201e45f4a619140630a88 | 08:56 |
| kata-irc-bot | -uuid 88b1ba1b-abda-440b-ad48-e53787288b39 -machine q35,accel=kvm,kernel_irqchip=on,nvdimm=on -cpu host, -qmp unix:/run/vc/vm/977c24e8414012d8116847b57b4a32ced3c21e94de0201e45f4a619140630a88/qmp.sock,server=on,wait=off -m 2048M,slots=10,maxmem=8865M -device pci-bridge,bus=pcie.0,id=pci-bridge-0,chassis_nr=1,shpc=off,addr=2,io-reserve=4k,mem-reserve=1m,pref64-reserve=1m -device virtio-serial-pci,disable-modern=false,id=serial0 -device | 08:56 |
| kata-irc-bot | virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/vc/vm/977c24e8414012d8116847b57b4a32ced3c21e94de0201e45f4a619140630a88/console.sock,server=on,wait=off -device nvdimm,id=nv0,memdev=mem0,unarmed=on -object memory-backend-file,id=mem0,mem-path=/home/kant/kata-containers.img,size=671088640,readonly=on -device virtio-scsi-pci,id=scsi0,disable-modern=false -object rng-random,id=rng0,filename=/dev/urandom | 08:56 |
| kata-irc-bot | -device virtio-rng-pci,rng=rng0 -device pcie-root-port,id=rp0,bus=pcie.0,chassis=0,slot=0,multifunction=off -device pcie-root-port,id=rp1,bus=pcie.0,chassis=0,slot=1,multifunction=off -device vhost-vsock-pci,disable-modern=false,vhostfd=3,id=vsock-3519019653,guest-cid=3519019653 -chardev socket,id=char-f747ffa68da33aef,path=/run/vc/vm/977c24e8414012d8116847b57b4a32ced3c21e94de0201e45f4a619140630a88/vhost-fs.sock -device | 08:56 |
| kata-irc-bot | vhost-user-fs-pci,chardev=char-f747ffa68da33aef,tag=kataShared,cache-size=1024M -netdev tap,id=network-0,vhost=on,vhostfds=4:5,fds=6:7 -device driver=virtio-net-pci,netdev=network-0,mac=1e:51:f7:19:84:7d,disable-modern=false,mq=on,vectors=6 -rtc base=utc,driftfix=slew,clock=host -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic --no-reboot -daemonize -object | 08:56 |
| kata-irc-bot | memory-backend-file,id=dimm1,size=2048M,mem-path=/dev/hugepages,share=on,prealloc=on -numa node,memdev=dimm1 -kernel /usr/share/kata-containers/vmlinuz-5.4.60.91-52.container -append tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k console=hvc0 console=hvc1 cryptomgr.notests net.ifnames=0 pci=lastbus=0 root=/dev/pmem0p1 | 08:56 |
| kata-irc-bot | rootflags=dax,data=ordered,errors=remount-ro ro rootfstype=ext4 debug systemd.show_status=true systemd.log_level=debug panic=1 nr_cpus=4 systemd.unit=kata-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket scsi_mod.scan=none agent.log=debug agent.log=debug agent.debug_console agent.debug_console_vport=1026 agent.hotplug_timeout=10 -pidfile | 08:56 |
| kata-irc-bot | /run/vc/vm/977c24e8414012d8116847b57b4a32ced3c21e94de0201e45f4a619140630a88/pid -D /run/vc/vm/977c24e8414012d8116847b57b4a32ced3c21e94de0201e45f4a619140630a88/qemu.log -smp 2,cores=1,threads=1,sockets=4,maxcpus=4]" name=containerd-shim-v2 pid=20854 sandbox=977c24e8414012d8116847b57b4a32ced3c21e94de0201e45f4a619140630a88 source=virtcontainers subsystem=qmp``` | 08:56 |
| kata-irc-bot | <christophe> I asked. Maybe update issue #1132 with the information above? | 17:26 |
| kata-irc-bot | <shuo.chen> @christophe I updated the issue with the above information. Do you know who is the best person to help us take a look? I suspect whether we are missing some parameter when building the qemu in our release artifact? | 19:39 |
| kata-irc-bot | <fidencio> @shuo.chen, that's interesting, looking at the files here I am having a hard time to figure out if we ever have shipped experimental content as part of kata-deploy. | 20:12 |
| kata-irc-bot | <fidencio> In case we want to do that, we'd need to: • build qemu-experimental as part of the release process (and also on every PR, to ensure that doesn't break); • build kernel-experimental (same as above) • have runtimeClasses for those • have different configuration files for kata-containers to use those | 20:13 |
| kata-irc-bot | <fidencio> But you can easily build it yourself using https://github.com/kata-containers/kata-containers/blob/ac058b389721242c3763be64bae4d805378f0622/tools/packaging/static-build/qemu/Makefile#L12 | 20:14 |
| kata-irc-bot | <fidencio> This fits here: https://github.com/kata-containers/kata-containers/issues/2772 | 20:15 |
| kata-irc-bot | <fidencio> In case you're willing to take a stab and implement it, I'd be happy to do a review on that | 20:15 |
| kata-irc-bot | <shuo.chen> I’m a little bit confused. Do you mean DAX support are currently in qemu experimental content which currently doesn’t include in the current artifacts? | 20:15 |
| kata-irc-bot | <fidencio> I mean, that *seems* to be the case | 20:16 |
| kata-irc-bot | <shuo.chen> yeah, if that is the case, I think we should say current release doesn’t support `virtio_fs_cache_size` in the configuration. | 20:17 |
| kata-irc-bot | <fidencio> And I am saying that based on https://github.com/kata-containers/kata-containers/commit/25670d3058e6aea02adc0ac380d3f83212099a36 | 20:17 |
| kata-irc-bot | <fidencio> > yeah, if that is the case, I think we should say current release doesn’t support `virtio_fs_cache_size` in the configuration. "support" is a hard term here. It does support depending on the QEMU and Kernel that you're using. | 20:17 |
| kata-irc-bot | <fidencio> But I agree with you, and I sincerely think we should be more vocal on what was tested and what's released. | 20:18 |
| kata-irc-bot | <fidencio> I'd love to see an issue about that, document better what's released and what is expected to work there. | 20:18 |
| kata-irc-bot | <shuo.chen> gotcha. would you mind help reopen the #1132 issue? I don’t have permission to do that, and we can use that to do further discussion | 20:19 |
| kata-irc-bot | <fidencio> Do you do a sum up there of what we talked here? | 20:20 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!