Comment 3 for bug 1663658

So the problem here is that `qemu-img info ...` call takes more than 8 seconds of CPU time (note, that it's not wall clock time, it's the time spent by CPU on execution of the process both in user and kernel spaces). The interesting part here is that in successful runs of the CI job the timings are much lower - this call usually takes <= 0.3s (the same is true for upstream CI). As long as we are using the same image (cirros) and the same qemu-img version across jobs runs the only difference is the environment state (RAM/swap usage, disk load, etc). Unfortunately, atop logs for this period of time are not available, so we can't tell for sure, what exactly causes slowness of qemu-img.

I glanced over the CI jobs failures and looks like this is only reproduced in Community builds: as we are using the same packages versions (both qemu-utils and cirros-testvm image), most likely the problem is in the CI node resources, specifically we run out of RAM and start using swap.