Julio Montes

@gorozco1 2.0 will be still compatible since it only needs systemd

qemu-lite 2.6.0 is working

qemu-lite 2.7.0 docker run fedora:25 dnf install rpm ``` BDB0126 mmap: Invalid argument *** Error in `/usr/bin/qemu-lite-system-x86_64': free(): invalid pointer: 0x000055a3d9504893 *** ======= Backtrace: ========= /usr/lib64/libc.so.6(+0x7c89b)[0x7fd21082589b] /usr/lib64/libc.so.6(+0x86a1a)[0x7fd21082fa1a] /usr/lib64/libc.so.6(cfree+0x5c)[0x7fd2108336fc] /usr/bin/qemu-lite-system-x86_64(+0x385de6)[0x55a3d950cde6] /usr/bin/qemu-lite-system-x86_64(+0x2680de)[0x55a3d93ef0de]...

great! thanks @mcastelino and nice description

still occurs using device driver overlay2

@rarindam nop, but I can try I tested with qemu 2.10.1 to see if it was fixed, but still occurs 😢

@rarindam what kernel did you use? would you mind running the iperf test? in clear containers this is the cmdline: ``` -device virtio-9p-pci,fsdev=ctr-9p-0,mount_tag=ctr-rootfs-0 -fsdev local,id=ctr-9p-0,path=/var/lib/docker/overlay2/232a11afb1dd6db15ef9a79d039c15ffdf85b09fea336420f5eb31eb186db2af/merged,security_model=none ```

``` - but I don't think we can trust it 100% to generate the final notes without human review. ``` agree, we can't trust

Hi @zgen0623 if you are using kata, then it's enabled by default. you can check it in your configuration file, see https://github.com/kata-containers/runtime/blob/master/cli/config/configuration-qemu.toml.in#L103

@tcheng8 not yet cc @bergwolf @WeiZhang555