Bug ID | 1131184 |
---|---|
Summary | virt-sysprep fails with OOM in "find0" |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Minor |
Priority | P5 - None |
Component | Virtualization:Tools |
Assignee | virt-bugs@suse.de |
Reporter | martin.wilck@suse.com |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
I have a small VM cloning script that calls virt-sysprep. When this script comes to the "cron-spool" action, it fails like this: > [ 9,2] Performing "cron-spool" ... > libguestfs: trace: is_dir "/var/spool/cron/" > guestfsd: <= is_dir (0x26) request length 64 bytes > chroot: /sysroot: running 'is_dir: /var/spool/cron/' > libguestfs: trace: is_dir = 1 > libguestfs: trace: find "/var/spool/cron/" > libguestfs: trace: find0 "/var/spool/cron/" "/tmp/libguestfsiFoKQK/find641.txt" > guestfsd: => is_dir (0x26) took 0.00 secs > guestfsd: <= find0 (0xc4) request length 60 bytes > find /sysroot/var/spool/cron/ -print0 > guestfsd: error: find /sysroot/var/spool/cron/ -print0: Cannot allocate memory > guestfsd: => find0 (0xc4) took 0.00 secs > libguestfs: trace: find0 = -1 (error) > libguestfs: trace: find = NULL (error) I have increased LIBGUESFS_MEMSIZE (aka --memsize for guestfish) from 500 to 4000, and still the same error occurs, so it does not seem to be caused by VM memory size. If I deactivate the "cron-spool" action, the failure occurs in another "find0" invocation: > [ 10,6] Performing "package-manager-cache" ... > ... > libguestfs: trace: find0 "/var/cache/zypp/" "/tmp/libguestfsi4Phc/find641.txt" guestfsd: => is_dir (0x26) took 0.00 secs > guestfsd: <= find0 (0xc4) request length 60 bytes > find /sysroot/var/cache/zypp/ -print0 > guestfsd: error: find /sysroot/var/cache/zypp/ -print0: Cannot allocate memory > guestfsd: => find0 (0xc4) took 0.00 secs If I remove the "package-manager-cache" action, too, the command succeeds.