qemu segfault (free(): invalid pointer) running dnf install #669

jcvenegas · 2017-02-15T19:42:17Z

When dnf is used to install a pakcage in a container it breaks all the container.

sudo docker run -ti fedora:25 dnf install rpm
BDB0126 mmap: Invalid argument
/usr/libexec/cc-shim: EOF received on proxy I/O fd

The text was updated successfully, but these errors were encountered:

devimc · 2017-02-15T19:46:46Z

qemu-lite 2.6.0 is working

jcvenegas · 2017-02-15T19:49:02Z

Adding @anthonyzxu

devimc · 2017-02-15T19:49:40Z

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]
/usr/bin/qemu-lite-system-x86_64(+0x29f2e7)[0x55a3d94262e7]
/usr/bin/qemu-lite-system-x86_64(+0x53d9a7)[0x55a3d96c49a7]
/usr/bin/qemu-lite-system-x86_64(+0x52ac6e)[0x55a3d96b1c6e]
/usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x282)[0x7fd210b309e2]
/usr/bin/qemu-lite-system-x86_64(+0x53b2a2)[0x55a3d96c22a2]
/usr/bin/qemu-lite-system-x86_64(+0x1e6464)[0x55a3d936d464]
/usr/lib64/libc.so.6(__libc_start_main+0xf1)[0x7fd2107c95d1]
/usr/bin/qemu-lite-system-x86_64(+0x1e8fda)[0x55a3d936ffda]
======= Memory map: ========
55a3d9187000-55a3d990d000 r-xp 00000000 08:03 5972169                    /usr/bin/qemu-lite-system-x86_64
55a3d990e000-55a3d9ac2000 r--p 00786000 08:03 5972169                    /usr/bin/qemu-lite-system-x86_64
55a3d9ac2000-55a3d9b1d000 rw-p 0093a000 08:03 5972169                    /usr/bin/qemu-lite-system-x86_64
55a3d9b1d000-55a3d9f4e000 rw-p 00000000 00:00 0 
55a3da209000-55a3dade8000 rw-p 00000000 00:00 0                          [heap]
7fd16c000000-7fd16c021000 rw-p 00000000 00:00 0 
7fd16c021000-7fd170000000 ---p 00000000 00:00 0 
7fd173e00000-7fd1f3e00000 rw-p 00000000 00:00 0 
7fd1f3e00000-7fd1f3e01000 ---p 00000000 00:00 0 
7fd1f4000000-7fd1f4021000 rw-p 00000000 00:00 0 
7fd1f4021000-7fd1f8000000 ---p 00000000 00:00 0 
7fd1f8000000-7fd1f8022000 rw-p 00000000 00:00 0 
7fd1f8022000-7fd1fc000000 ---p 00000000 00:00 0 
7fd1fc000000-7fd1fc748000 rw-p 00000000 00:00 0 
7fd1fc748000-7fd200000000 ---p 00000000 00:00 0 
7fd200a00000-7fd200a40000 rw-p 00000000 00:00 0 
7fd200a40000-7fd200a41000 ---p 00000000 00:00 0 
7fd200bba000-7fd200bda000 rw-s 00000000 00:05 90543                      /dev/zero (deleted)
7fd200bda000-7fd200bdb000 ---p 00000000 00:00 0 
7fd200bdb000-7fd200d0a000 rw-p 00000000 00:00 0 
7fd200d19000-7fd200d59000 rw-s 00000000 00:05 90542                      /dev/zero (deleted)
7fd200d59000-7fd200d5a000 ---p 00000000 00:00 0 
7fd200d5a000-7fd200d5b000 ---p 00000000 00:00 0 
7fd200d5b000-7fd20155b000 rw-p 00000000 00:00 0 
7fd20155b000-7fd20155c000 ---p 00000000 00:00 0 
7fd20155c000-7fd201e1f000 rw-p 00000000 00:00 0 
7fd201e1f000-7fd20ff1f000 rw-p 00000000 08:03 5898297                    /usr/share/clear-containers/clear-13280-containers.img
7fd20ff1f000-7fd20ff20000 ---p 00000000 00:00 0 
7fd20ff20000-7fd20ff21000 ---p 00000000 00:00 0 
7fd20ff21000-7fd210726000 rw-p 00000000 00:00 0 
7fd210726000-7fd2107a6000 r-xp 00000000 08:03 5915433                    /usr/lib64/libpcre.so.1.2.8
7fd2107a6000-7fd2107a7000 ---p 00080000 08:03 5915433                    /usr/lib64/libpcre.so.1.2.8
7fd2107a7000-7fd2107a8000 r--p 00080000 08:03 5915433                    /usr/lib64/libpcre.so.1.2.8
7fd2107a8000-7fd2107a9000 rw-p 00081000 08:03 5915433                    /usr/lib64/libpcre.so.1.2.8
7fd2107a9000-7fd21096c000 r-xp 00000000 08:03 5927243                    /usr/lib64/libc-2.25.so
7fd21096c000-7fd21096d000 ---p 001c3000 08:03 5927243                    /usr/lib64/libc-2.25.so
7fd21096d000-7fd210971000 r--p 001c3000 08:03 5927243                    /usr/lib64/libc-2.25.so
7fd210971000-7fd210973000 rw-p 001c7000 08:03 5927243                    /usr/lib64/libc-2.25.so
7fd210973000-7fd210977000 rw-p 00000000 00:00 0 
7fd210977000-7fd210991000 r-xp 00000000 08:03 5927315                    /usr/lib64/libpthread-2.25.so
7fd210991000-7fd210992000 r--p 00019000 08:03 5927315                    /usr/lib64/libpthread-2.25.so
7fd210992000-7fd210993000 rw-p 0001a000 08:03 5927315                    /usr/lib64/libpthread-2.25.so
7fd210993000-7fd210997000 rw-p 00000000 00:00 0 
7fd210997000-7fd2109ae000 r-xp 00000000 08:03 5908101                    /usr/lib64/libgcc_s.so.1
7fd2109ae000-7fd2109af000 r--p 00016000 08:03 5908101                    /usr/lib64/libgcc_s.so.1
7fd2109af000-7fd2109b0000 rw-p 00017000 08:03 5908101                    /usr/lib64/libgcc_s.so.1
7fd2109b0000-7fd210ac4000 r-xp 00000000 08:03 5927307                    /usr/lib64/libm-2.25.so
7fd210ac4000-7fd210ac5000 r--p 00113000 08:03 5927307                    /usr/lib64/libm-2.25.so
7fd210ac5000-7fd210ac6000 rw-p 00114000 08:03 5927307                    /usr/lib64/libm-2.25.so
7fd210ac6000-7fd210acd000 r-xp 00000000 08:03 5927266                    /usr/lib64/librt-2.25.so
7fd210acd000-7fd210ace000 r--p 00006000 08:03 5927266                    /usr/lib64/librt-2.25.so
7fd210ace000-7fd210acf000 rw-p 00007000 08:03 5927266                    /usr/lib64/librt-2.25.so
7fd210acf000-7fd210ad1000 rw-p 00000000 00:00 0 
7fd210ad1000-7fd210c18000 r-xp 00000000 08:03 5921771                    /usr/lib64/libglib-2.0.so.0.5000.3
7fd210c18000-7fd210c19000 r--p 00146000 08:03 5921771                    /usr/lib64/libglib-2.0.so.0.5000.3
7fd210c19000-7fd210c1a000 rw-p 00147000 08:03 5921771                    /usr/lib64/libglib-2.0.so.0.5000.3
7fd210c1a000-7fd210c24000 r-xp 00000000 08:03 5943262                    /usr/lib64/libnuma.so.1.0.0
7fd210c24000-7fd210c25000 ---p 0000a000 08:03 5943262                    /usr/lib64/libnuma.so.1.0.0
7fd210c25000-7fd210c26000 r--p 0000a000 08:03 5943262                    /usr/lib64/libnuma.so.1.0.0
7fd210c26000-7fd210c27000 rw-p 0000b000 08:03 5943262                    /usr/lib64/libnuma.so.1.0.0
7fd210c27000-7fd210c29000 r-xp 00000000 08:03 5927253                    /usr/lib64/libutil-2.25.so
7fd210c29000-7fd210c2a000 ---p 00002000 08:03 5927253                    /usr/lib64/libutil-2.25.so
7fd210c2a000-7fd210c2b000 r--p 00002000 08:03 5927253                    /usr/lib64/libutil-2.25.so
7fd210c2b000-7fd210c2c000 rw-p 00003000 08:03 5927253                    /usr/lib64/libutil-2.25.so
7fd210c2c000-7fd210d5a000 r-xp 00000000 08:03 5908613                    /usr/lib64/libpixman-1.so.0.34.0
7fd210d5a000-7fd210d5b000 ---p 0012e000 08:03 5908613                    /usr/lib64/libpixman-1.so.0.34.0
7fd210d5b000-7fd210d63000 r--p 0012e000 08:03 5908613                    /usr/lib64/libpixman-1.so.0.34.0
7fd210d63000-7fd210d64000 rw-p 00136000 08:03 5908613                    /usr/lib64/libpixman-1.so.0.34.0
7fd210d64000-7fd210d92000 r-xp 00000000 08:03 5909175                    /usr/lib64/libz.so.1.2.8
7fd210d92000-7fd210d93000 r--p 0002d000 08:03 5909175                    /usr/lib64/libz.so.1.2.8
7fd210d93000-7fd210d94000 rw-p 0002e000 08:03 5909175                    /usr/lib64/libz.so.1.2.8
7fd210da0000-7fd210da1000 rw-p 00000000 00:00 0 
7fd210da1000-7fd210da4000 rw-s 00000000 00:0c 12074                      anon_inode:kvm-vcpu
7fd210da4000-7fd210da7000 rw-s 00000000 00:0c 12074                      anon_inode:kvm-vcpu
7fd210da7000-7fd210da8000 rw-s 00000000 00:05 89707                      /dev/zero (deleted)
7fd210da8000-7fd210dab000 rw-s 00000000 00:05 91202                      /dev/zero (deleted)
7fd210dab000-7fd210dad000 rw-p 00000000 00:00 0 
7fd210dad000-7fd210dd3000 r-xp 00000000 08:03 5927286                    /usr/lib64/ld-2.25.so
7fd210dd3000-7fd210dd4000 rw-s 00000000 00:05 89706                      /dev/zero (deleted)
7fd210dd4000-7fd210dd5000 r--p 00026000 08:03 5927286                    /usr/lib64/ld-2.25.so
7fd210dd5000-7fd210dd7000 rw-p 00027000 08:03 5927286                    /usr/lib64/ld-2.25.so
7ffc28d4d000-7ffc28d6e000 rw-p 00000000 00:00 0                          [stack]
7ffc28dc8000-7ffc28dca000 r--p 00000000 00:00 0                          [vvar]
7ffc28dca000-7ffc28dcc000 r-xp 00000000 00:00 0                          [vdso]
/usr/libexec/cc-shim: EOF received on proxy I/O fd

jodh-intel · 2017-02-20T18:11:20Z

A few more data points:

dnf search foo: crash.
dnf list: crash.
rpm -qa: OK.

dnf --version: Error, but no crash.

 1.1.10
 BDB0126 mmap: Invalid argument
 Failed loading RPMDB.

behaviour is consistent in fedora:25, fedora:24 and fedora:23.
I tried installing strace in a container, committing, then running strace dnf ... but no longer see the issue.

grahamwhaley · 2017-02-20T18:18:32Z

I suspect this is not the same as the 9p stuff we've seen in the past affecting apt-get - but, just as a test, you could try mounting /tmp onto a ramfs to remove 9p from the equation there - that fixed the 9p issues before... (but @jodh-intel knows that already ;-)

jodh-intel · 2017-02-21T08:50:05Z

Looks like we are indeed back in 9p territory...

Incorrect behaviour:

$ sudo docker run -ti fedora bash -c 'dnf install foo'
BDB0126 mmap: Invalid argument
/usr/libexec/cc-shim: EOF received on proxy I/O fd

But with a non-9p /tmp, dnf's behaviour is correct (although we still see the mmap error):

$ sudo docker run -ti fedora bash -c 'mount -t ramfs -o size=20M ramfs /tmp && dnf install foo'
BDB0126 mmap: Invalid argument
Fedora 25 - x86_64 - Updates                                                                                                                                   304 kB/s |  18 MB     01:02    
Fedora 25 - x86_64                                                                                                                                             353 kB/s |  50 MB     02:26    
Last metadata expiration check: 0:01:21 ago on Tue Feb 21 08:43:27 2017.
No package foo available.
Error: Unable to find a match.

gorozco1 · 2017-04-11T22:26:33Z

Anyone knows if this is also happening with debian based distros? what about doing apt-get install ?

gorozco1 · 2017-04-11T22:28:08Z

@anthonyzxu do you have any update?

@ALL how critical is this issue?

jodh-intel · 2017-04-12T08:05:52Z

I think the P2 label is valid: it should not be possible for an arbitrary command (particularly a commonly-used one like dnf for Fedora) to kill the hypervisor.

It's not a P1 for 2 reasons:

It's still possible to create and start a Fedora container (with the caveat that you cannot run dnf install).
There is a workaround for the issue.

@anthonyzxu - this issue has been open for almost 2 months now: could you give an update please?

** Changes - Devicemapper storage - version: Update container image to 16020 - obs: Update packaging to include kernel config changes for xfs - cc-oci-runtime.sh: Enable debug by default - configure: Add warning when kernel or image is not found - proxy: Better error message for too long socket path - tests: metrics: formalise the metrics reporting methods - build: Adds option to install kernel and image ** Shortlog 271223a tests: Skip docker cp integration test for devicemapper storage 9b91166 tests: Fix functional tests to include workload directory 66cbd66 tests: Fix state tests and add check for workload_dir. b8ffdb1 tests: Fix mounts test for unmounting volume. 97922b5 storage: Pass drive name to hyperstart with the newcontainer command dd13e32 storage: Pass block device to qemu if found. b95748f state: Store the block storage device file system type and index 2d783ae storage: Add function to check the storage for container rootfs e05e368 mount: Add function to return the device name and file system type b1768e8 mount: Add function to get the mount point given a path f9c0d36 storage: Add function to check if device is a devicemapper device 2c8374d mount: Add function to get underlying device for a path. 69abef6 state: Update the rootfs and workload dir config from state f202ba4 namespace: Do not join mount namespace while unmounting. 9d8a083 mounts: Unmount the container rootfs 61b8b8b proxy: Pass hyperstart fsmap array with newcontainer command. 27f25fc proxy: Pass shared directory to hyperstart. 0af8583 state: Store the workload dir and rootfs mount to state. 53dc5ff state: Add the host_path and mnt_dir field to state. 4bb2d17 mounts: Bind mount container rootfs to workload directory 65d5eb4 config: Add a new field "workload_dir" to config for the worload path fb9f94e mounts: Factorise the pod function for bind-mouting rootfs 5249cb4 9pfs: Dynamically add 9pfs options to qemu. 0ef2f8c version: Update container image to version 16020 b1fcd2a obs: Update packaging to include kernel config changes for xfs 567127f cc-oci-runtime.sh: Enable debug by default 053ea8e tests: Fix make discheck running proxy d10dc46 configure: Add warning when kernel or image is not found c543dcb proxy: Better error message for too long socket path 5b83071 tests: metrics: density: Use the new metrics reporting function 35de59e tests: metrics: Update README with details of new infra 9a4daf9 tests: metrics: Add script to save results into csv 827347d tests: common: Add new method for saving results 68c2673 build: Adds option to install kernel and image ** Compatibility with Docker Clear Containers 2.2.0 is compatible with Docker v17.05.0-ce ** OCI Runtime Specification Clear Containers 2.2.0 support the OCI Runtime Specification [1.0.0-rc5][ocispec] ** Clear Linux Containers image Clear Containers 2.2.0 requires at least Clear Linux containers image [16020][clearlinuximage] ** Clear Linux Containers Kernel Clear Containers 2.2.0 requires at least Clear Linux Containers kernel 4.9.33-74 * Installation - [Centos][centos] - [Ubuntu][ubuntu] - [Fedora][fedora] - [Clear Linux][clearlinux] * Issues & limitations - Qemu segfault (free(): invalid pointer) running dnf install intel#669 - DNS Resolution in Swarm intel#854 - docker rm -f reports 'Driver devicemapper failed to remove root filesystem' intel#795 [centos]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Centos-7.md [ubuntu]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Ubuntu.md [fedora]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Fedora.md [clearlinux]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-ClearLinux.md [clearlinuximage]: https://download.clearlinux.org/releases/16020/clear/clear-16020-containers.img.xz [ocispec]: https://github.com/opencontainers/runtime-spec/releases/tag/v1.0.0-rc5 Fixes: intel#1003 Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>

jcvenegas · 2017-06-22T19:09:53Z

After merge the support to use devicemapper volumes as storage device , this issue only happen in non-devicemapper rootfs. It is recommended to use devicemapper for a better filesystem compliance.

egernst · 2017-06-22T19:17:19Z

Sure, though this is still an open 9p issue for all other systems, and likely if we mount a volume still using 9p. On Jun 22, 2017, at 12:10 PM, Jose Carlos Venegas Munoz <notifications@github.com<mailto:notifications@github.com>> wrote: After merge the support to use devicemapper volumes as storage device , this issue only happen in non-devicemapper rootfs. It is recommended to use devicemapper for a better filesystem compliance. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub<#669 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ATPXWwYlyPaxDIANduxTLKfgyLgDsYuXks5sGrwGgaJpZM4MCKIF>.

* Release 2.2.0 ** Changes - versions: update kernel to linux-container-4.9.34-75 - shim: Add command line option to show version information - storage: Perform sync operation before vm is shutdown - tests: Use nginx:1.13.0 for swarm tests - proxy: Lift the numbers of opened file descriptors limit - CI: Enforce checkcommits. - Fix unnecessary bash-isms in installation script ** Shortlog 3eeda89 versions: update kernel to linux-container-4.9.34-75 4e8f155 version: Add command line option to show version information 21b874a storage: Perform sync operation before vm is shutdown 191e9f8 tests: Use nginx:1.13.0 for swarm tests 2f22de2 proxy: Lift the numbers of opened file descriptors limit 55eba02 CI: Enforce checkcommits. 6566262 Fix unnecessary bash-isms in installation script ** Compatibility with Docker Clear Containers 2.2.0 is compatible with Docker v17.05.0-ce ** OCI Runtime Specification Clear Containers 2.2.0 support the OCI Runtime Specification [1.0.0-rc5][ocispec] ** Clear Linux Containers image Clear Containers 2.2.0 requires at least Clear Linux containers image [16160][clearlinuximage] ** Clear Linux Containers Kernel Clear Containers 2.2.0 requires at least Clear Linux Containers kernel 4.9.34-75 * Installation - [Centos][centos] - [Ubuntu][ubuntu] - [Fedora][fedora] - [Clear Linux][clearlinux] * Issues & limitations - Qemu segfault (free(): invalid pointer) running dnf install intel#669 - DNS Resolution in Swarm intel#854 - docker rm -f reports 'Driver devicemapper failed to remove root filesystem' intel#795 [centos]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Centos-7.md [ubuntu]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Ubuntu.md [fedora]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Fedora.md [clearlinux]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-ClearLinux.md [clearlinuximage]: https://download.clearlinux.org/releases/16160/clear/clear-16160-containers.img.xz [ocispec]: https://github.com/opencontainers/runtime-spec/releases/tag/v1.0.0-rc5 Fixes: intel#1022 Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>

* Release 2.2.2 ** Changes - versions: update kernel to linux-container-4.9.34-75 - shim: Add command line option to show version information - storage: Perform sync operation before vm is shutdown - tests: Use nginx:1.13.0 for swarm tests - proxy: Lift the numbers of opened file descriptors limit - CI: Enforce checkcommits. - Fix unnecessary bash-isms in installation script ** Shortlog 3eeda89 versions: update kernel to linux-container-4.9.34-75 4e8f155 version: Add command line option to show version information 21b874a storage: Perform sync operation before vm is shutdown 191e9f8 tests: Use nginx:1.13.0 for swarm tests 2f22de2 proxy: Lift the numbers of opened file descriptors limit 55eba02 CI: Enforce checkcommits. 6566262 Fix unnecessary bash-isms in installation script ** Compatibility with Docker Clear Containers 2.2.1 is compatible with Docker v17.05.0-ce ** OCI Runtime Specification Clear Containers 2.2.1 support the OCI Runtime Specification [1.0.0-rc5][ocispec] ** Clear Linux Containers image Clear Containers 2.2.1 requires at least Clear Linux containers image [16160][clearlinuximage] ** Clear Linux Containers Kernel Clear Containers 2.2.1 requires at least Clear Linux Containers kernel 4.9.34-75 * Installation - [Centos][centos] - [Ubuntu][ubuntu] - [Fedora][fedora] - [Clear Linux][clearlinux] * Issues & limitations - Qemu segfault (free(): invalid pointer) running dnf install intel#669 - DNS Resolution in Swarm intel#854 - docker rm -f reports 'Driver devicemapper failed to remove root filesystem' intel#795 [centos]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Centos-7.md [ubuntu]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Ubuntu.md [fedora]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Fedora.md [clearlinux]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-ClearLinux.md [clearlinuximage]: https://download.clearlinux.org/releases/16160/clear/clear-16160-containers.img.xz [ocispec]: https://github.com/opencontainers/runtime-spec/releases/tag/v1.0.0-rc5 Fixes: intel#1022 Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>

* Release 2.2.2 ** Changes - artifacts: Remove OBS common artifacsts between 2.x and 3.x - versions: Update kernel and image versions - Tests: Change nginx image for swarm tests - install: Extract autoconf-archive install to separate script ** Shortlog ef8144e artifacts: Remove OBS common artifacsts between 2.x and 3.x 73e28fe versions: Update kernel and image versions 3a9e3d7 Tests: Change nginx image for swarm tests 82cfb1f install: Extract autoconf-archive install to separate script ** Compatibility with Docker Clear Containers 2.2.2 is compatible with Docker v17.05.0-ce ** OCI Runtime Specification Clear Containers 2.2.2 support the OCI Runtime Specification [1.0.0-rc5][ocispec] ** Clear Linux Containers image Clear Containers 2.2.2 requires at least Clear Linux containers image [16180][clearlinuximage] ** Clear Linux Containers Kernel Clear Containers 2.2.2 requires at least Clear Linux Containers kernel 4.9.35-76 * Installation - [Centos][centos] - [Ubuntu][ubuntu] - [Fedora][fedora] - [Clear Linux][clearlinux] * Issues & limitations - Qemu segfault (free(): invalid pointer) running dnf install intel#669 - DNS Resolution in Swarm intel#854 - docker rm -f reports 'Driver devicemapper failed to remove root filesystem' intel#795 [centos]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Centos-7.md [ubuntu]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Ubuntu.md [fedora]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Fedora.md [clearlinux]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-ClearLinux.md [clearlinuximage]: https://download.clearlinux.org/releases/16180/clear/clear-16180-containers.img.xz [ocispec]: https://github.com/opencontainers/runtime-spec/releases/tag/v1.0.0-rc5 Fixes: intel#1033 Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>

* Release 2.2.3 ** Changes - tests: Dockerfile for Nginx for swarm tests - delete: Fail if try to delete a non-stopped container. ** Shortlog 91aacdf tests: Dockerfile for Nginx for swarm tests 5121969 delete: allow destroy_pod fail if vm die 29f8aa2 tests: functional: check delete fails without kill a51537c delete: Delete container only if state is STOPPED ** Compatibility with Docker Clear Containers 2.2.3 is compatible with Docker v17.05.0-ce ** OCI Runtime Specification Clear Containers 2.2.3 support the OCI Runtime Specification [1.0.0-rc5][ocispec] ** Clear Linux Containers image Clear Containers 2.2.3 requires at least Clear Linux containers image [16180][clearlinuximage] ** Clear Linux Containers Kernel Clear Containers 2.2.3 requires at least Clear Linux Containers kernel 4.9.35-76 * Installation - [Centos][centos] - [Ubuntu][ubuntu] - [Fedora][fedora] - [Clear Linux][clearlinux] * Issues & limitations - Qemu segfault (free(): invalid pointer) running dnf install intel#669 - DNS Resolution in Swarm intel#854 - docker rm -f reports 'Driver devicemapper failed to remove root filesystem' intel#795 [centos]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Centos-7.md [ubuntu]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Ubuntu.md [fedora]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Fedora.md [clearlinux]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-ClearLinux.md [clearlinuximage]: https://download.clearlinux.org/releases/16180/clear/clear-16180-containers.img.xz [ocispec]: https://github.com/opencontainers/runtime-spec/releases/tag/v1.0.0-rc5 Fixes: intel#1040 Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>

** Changes - tests: Dockerfile for Nginx for swarm tests - delete: Fail if try to delete a non-stopped container. ** Shortlog 91aacdf tests: Dockerfile for Nginx for swarm tests 5121969 delete: allow destroy_pod fail if vm die 29f8aa2 tests: functional: check delete fails without kill a51537c delete: Delete container only if state is STOPPED ** Compatibility with Docker Clear Containers 2.2.3 is compatible with Docker v17.05.0-ce ** OCI Runtime Specification Clear Containers 2.2.3 support the OCI Runtime Specification [1.0.0-rc5][ocispec] ** Clear Linux Containers image Clear Containers 2.2.3 requires at least Clear Linux containers image [16180][clearlinuximage] ** Clear Linux Containers Kernel Clear Containers 2.2.3 requires at least Clear Linux Containers kernel 4.9.35-76 * Installation - [Centos][centos] - [Ubuntu][ubuntu] - [Fedora][fedora] - [Clear Linux][clearlinux] * Issues & limitations - Qemu segfault (free(): invalid pointer) running dnf install intel#669 - DNS Resolution in Swarm intel#854 - docker rm -f reports 'Driver devicemapper failed to remove root filesystem' intel#795 [centos]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Centos-7.md [ubuntu]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Ubuntu.md [fedora]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Fedora.md [clearlinux]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-ClearLinux.md [clearlinuximage]: https://download.clearlinux.org/releases/16180/clear/clear-16180-containers.img.xz [ocispec]: https://github.com/opencontainers/runtime-spec/releases/tag/v1.0.0-rc5 Fixes: intel#1040 Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>

rarindam · 2017-07-28T19:41:50Z

As pointed out in #949, this also seems an mmap related issue.
Please try out with
mount -t 9p -o trans=virtio test_mount /tmp/shared/ -oversion=9p2000.L,cache=fscache

Cache=fscache is the main option that needs to be there if you want mmap write to be working.

** Changes - versions: Update image to version 16670 - OBS: add dependencies' versions - documentation: ciao-down prepare is now ciao-down create ** Shortlog cbdfd1d versions: Update image to version 16670 2c13fb1 OBS: add dependencies' versions 68d00dc documentation: Add the -u flag when go getting ciao-down 0c9d6bb documentation: ciao-down prepare is now ciao-down create ** Compatibility with Docker Clear Containers 2.2.4 is compatible with Docker v17.05.0-ce ** OCI Runtime Specification Clear Containers 2.2.4 support the OCI Runtime Specification [1.0.0-rc5][ocispec] ** Clear Linux Containers image Clear Containers 2.2.4 requires at least Clear Linux containers image [16670][clearlinuximage] ** Clear Linux Containers Kernel Clear Containers 2.2.4 requires at least Clear Linux Containers kernel 4.9.35-76 * Installation - [Centos][centos] - [Ubuntu][ubuntu] - [Fedora][fedora] - [Clear Linux][clearlinux] * Issues & limitations - Qemu segfault (free(): invalid pointer) running dnf install intel#669 - DNS Resolution in Swarm intel#854 - docker rm -f reports 'Driver devicemapper failed to remove root filesystem' intel#795 compatibility with docker 17.06 intel#1021 [centos]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Centos-7.md [ubuntu]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Ubuntu.md [fedora]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-Fedora.md [clearlinux]: https://github.com/01org/cc-oci-runtime/blob/master/documentation/Installing-Clear-Containers-on-ClearLinux.md [clearlinuximage]: https://download.clearlinux.org/releases/16670/clear/clear-16670-containers.img.xz [ocispec]: https://github.com/opencontainers/runtime-spec/releases/tag/v1.0.0-rc5 Fixes: intel#1050 Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>

jodh-intel changed the title ~~dnf install breask CC 2.1~~ dnf install breaks CC 2.1 Feb 15, 2017

jcvenegas changed the title ~~dnf install breaks CC 2.1~~ qemu segfault (free(): invalid pointer) running dnf install Feb 15, 2017

devimc assigned anthonyzxu Feb 17, 2017

jodh-intel added P2 type:bug domain:VM labels Feb 20, 2017

devimc self-assigned this Feb 28, 2017

jcvenegas mentioned this issue Apr 7, 2017

Docker build fails with Clear Containers as default clearcontainers/osbuilder#8

Open

jcvenegas added P1 and removed P2 labels May 3, 2017

This was referenced Jun 8, 2017

Release: 2.1.11 #970

Merged

Release 2.1.12 #993

Merged

jcvenegas mentioned this issue Jun 22, 2017

release: 2.2.0 #1005

Merged

jcvenegas assigned egernst and unassigned devimc Jun 22, 2017

jcvenegas mentioned this issue Jun 29, 2017

release: 2.2.1 #1025

Merged

jcvenegas mentioned this issue Jul 6, 2017

release: version 2.2.2 #1037

Merged

jcvenegas mentioned this issue Jul 13, 2017

Release 2.2.3 #1041

Merged

egernst added the CC 2.1 label Jul 18, 2017

jcvenegas mentioned this issue Jul 28, 2017

Release 2.2.4 #1052

Merged

jcvenegas mentioned this issue Aug 28, 2017

config: enable 9P_FSCACHE clearcontainers/linux#3

Closed

jodh-intel mentioned this issue Dec 19, 2017

no able to perform a dnf update in a fedora container clearcontainers/runtime#868

Open

bhydex unassigned anthonyzxu Jan 16, 2018

jodh-intel mentioned this issue Jul 6, 2018

Run docker in kata container kata-containers/runtime#358

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

qemu segfault (free(): invalid pointer) running dnf install #669

qemu segfault (free(): invalid pointer) running dnf install #669

jcvenegas commented Feb 15, 2017

devimc commented Feb 15, 2017

jcvenegas commented Feb 15, 2017

devimc commented Feb 15, 2017

jodh-intel commented Feb 20, 2017

grahamwhaley commented Feb 20, 2017

jodh-intel commented Feb 21, 2017 •

edited

Loading

gorozco1 commented Apr 11, 2017

gorozco1 commented Apr 11, 2017

jodh-intel commented Apr 12, 2017

jcvenegas commented Jun 22, 2017

egernst commented Jun 22, 2017 via email

rarindam commented Jul 28, 2017 •

edited

Loading

qemu segfault (free(): invalid pointer) running dnf install #669

qemu segfault (free(): invalid pointer) running dnf install #669

Comments

jcvenegas commented Feb 15, 2017

devimc commented Feb 15, 2017

jcvenegas commented Feb 15, 2017

devimc commented Feb 15, 2017

jodh-intel commented Feb 20, 2017

grahamwhaley commented Feb 20, 2017

jodh-intel commented Feb 21, 2017 • edited Loading

gorozco1 commented Apr 11, 2017

gorozco1 commented Apr 11, 2017

jodh-intel commented Apr 12, 2017

jcvenegas commented Jun 22, 2017

egernst commented Jun 22, 2017 via email

rarindam commented Jul 28, 2017 • edited Loading

jodh-intel commented Feb 21, 2017 •

edited

Loading

rarindam commented Jul 28, 2017 •

edited

Loading