On Thu, Jul 19, 2018 at 09:50:00PM +0300, Nir Soffer wrote: > On Mon, Jul 16, 2018 at 11:56 AM Daniel P. Berrangé <berra...@redhat.com> > wrote: > ... > > > Recommendation is to run 'qemu-img info' to extract the metadata and sanity > > check results eg no backing file list, not unreasonable size, etc. When > > running 'qemu-img info' apply process limits of 30 secs CPU time, and 1 GB > > address space. > > > > Can you explain the values of cpu seconds and addres space? > > Also, I tried to use prlimit --rss=N, and the value seems to be ignored. Is > this > a bug in prlimit?
This is the code in OpenStack: https://github.com/openstack/nova/blob/50f40854b04351fb622fd8b68b374a8fe8ca2070/nova/virt/images.py#L74 https://github.com/openstack/oslo.concurrency/blob/a9d728b71e47540fd248a6bc2d301fdfa9a988ce/oslo_concurrency/processutils.py#L194 (see prlimit) HTH, Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW