diff options
| -rwxr-xr-x | ironic_python_agent/shell/write_image.sh | 9 | ||||
| -rw-r--r-- | releasenotes/notes/limit-qemu-img-malloc-arena-025ed84115481eae.yaml | 7 |
2 files changed, 16 insertions, 0 deletions
diff --git a/ironic_python_agent/shell/write_image.sh b/ironic_python_agent/shell/write_image.sh index bcd6bfd3..16fcb903 100755 --- a/ironic_python_agent/shell/write_image.sh +++ b/ironic_python_agent/shell/write_image.sh @@ -49,6 +49,15 @@ log "Imaging $IMAGEFILE to $DEVICE" # limit the memory usage for qemu-img to 2 GiB ulimit -v 2097152 +# NOTE(TheJulia): qemu-img uses multiple threads by default and in +# cross-thread memory allocation lock conflicts, glibc will ultimately +# attempt to provide it with an additional arena to allocate from, however +# the running default, when not overridden is 8 * ncpu * the footprint, which +# very quickly exceeds the ulimit. This is most observable on CI systems where +# cross-vcpu thread locking can result in a conflict that wouldn't normally be +# as likely on physical hardware. +# See discussion on https://bugzilla.redhat.com/show_bug.cgi?id=1892773 +export MALLOC_ARENA_MAX=3 qemu-img convert -t directsync -O host_device $IMAGEFILE $DEVICE sync diff --git a/releasenotes/notes/limit-qemu-img-malloc-arena-025ed84115481eae.yaml b/releasenotes/notes/limit-qemu-img-malloc-arena-025ed84115481eae.yaml new file mode 100644 index 00000000..38ddf24e --- /dev/null +++ b/releasenotes/notes/limit-qemu-img-malloc-arena-025ed84115481eae.yaml @@ -0,0 +1,7 @@ +--- +fixes: + - | + Fixes failures with disk image conversions which result in memory + allocation or input/output errors due to memory limitations by limiting + the number of available memory allocation pools to a non-dynamic + reasonable number which should not exceed the available system memory. |