Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionRichard W.M. Jones
2014-06-25 11:32:47 UTC
+++ This bug was initially created as a clone of Bug #1099172 +++
Description of problem:
(Reported by Stef Walter)
mkdir -p ~/.guestfs-1000
/usr/bin/supermin --build --verbose --if-newer --lock ~/.guestfs-1000/lock --copy-kernel -f ext2 --host-cpu x86_64 /usr/lib64/guestfs/supermin.d -o ~/.guestfs-1000/appliance.d
fails with the error:
supermin: exception: Out of memory
I asked Stef to use -v -v -v, and the end of the output is:
- /var/lib/systemd/coredump
- /var/lib/systemd/random-seed
- /var/lib/tpm
- /var/local
- /var/lock
- /var/log
- /var/log/README
- /var/log/journal
- /var/log/lastlog
- /var/log/tallylog
- /var/spool
- /var/spool/mail
- /var/mail
- /var/nis
- /var/opt
- /var/preserve
- /var/run
- /var/run/console
- /var/run/dbus
- /var/run/faillock
- /var/run/mdadm
- /var/run/sepermit
- /var/run/setrans
- /var/spool
- /var/spool/lpd
- /var/spool/mail
- /var/tmp
- /var/yp
supermin: kernel: picked kernel vmlinuz-3.14.4-200.fc20.x86_64
supermin: kernel: picked modules path /lib/modules/3.14.4-200.fc20.x86_64
supermin: kernel: kernel_version 3.14.4-200.fc20.x86_64
supermin: kernel: modules /lib/modules/3.14.4-200.fc20.x86_64
supermin: ext2: creating empty ext2 filesystem '/data/.guestfs-1000/appliance.d.ci1uy50n/root'
mke2fs 1.42.8 (20-Jun-2013)
Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
262144 inodes, 1048576 blocks
52428 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1073741824
32 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
supermin: ext2: populating from base image
supermin: ext2: copying files from host filesystem
supermin: exception: Out of memory
It turns out the exception is raised from C code:
/* Read in the whole file into memory. Check the size is still 'size'. */
static char *
read_whole_file (const char *filename, size_t size)
{
char *buf = malloc (size);
if (buf == NULL)
caml_raise_out_of_memory ();
/var/log/lastlog (in this case) was a huge file which caused
the out of memory error.
Version-Release number of selected component (if applicable):
supermin 5.1.7
Comment 3Richard W.M. Jones
2014-07-21 07:19:22 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHEA-2016-2154.html