Large VM Images
Measured time, memory and disk space for building an SBOM from a 20 GB QCOW2, VMDK or OVA image with the Safeguard CLI, and the settings to use
Large VM Images
The Safeguard CLI reads VM disk images directly, without mounting them, and lists the operating system packages and applications inside. This page gives measured numbers for one 20 GiB image in three formats and the settings that were needed, so you can plan disk space and time before you scan an image of this size.
Tested results
Measured in November 2026 on a 16-core ARM64 Linux host with
safeguard sbom --dir <image> --sbom-format both. The image is a 20 GiB Linux
system with 668 known packages. All 668 were found in every format, with the
right version on 99 percent of them, and both the SPDX and the CycloneDX
document passed validation.
| Format | Image file | Size setting | Time | Peak memory | Temporary disk space | Output |
|---|---|---|---|---|---|---|
| QCOW2 | 18.1 GiB | none | 9 min 2 s | 1.3 GiB | 18.7 GiB | 7 MB |
| VMDK | 18.1 GiB | none | 8 min 44 s | 1.3 GiB | 19.5 GiB | 7 MB |
| OVA | 6.4 GiB, with a 20 GiB disk inside | SAFEGUARD_UNPACK_MAX_GB=48 | 22 min 24 s | 1.2 GiB | 42.6 GiB | 7 MB |
Times depend on how busy the host and its disk are. An earlier VMDK run of the same image on a busier host took 31 min 44 s.
Sizes are in GiB (binary gigabytes), the unit the size setting uses.
An OVA needs more temporary space than the other two formats because the disk is first copied out of the archive and then read.
Scan a large image
For a QCOW2 or VMDK file you do not need a size setting. When you give the CLI one file of 1 GiB or more, it sizes its unpack budget and its time limit from the file.
- Make sure the temporary directory has free space of about the virtual size
of the disk. Point
TMPDIRat a larger volume if the default one is small. - Run the scan on the image file itself:
export TMPDIR=/data/scan-tmp
safeguard sbom --dir appliance.qcow2 --sbom-format bothAn OVA, or any image that is compressed inside an archive, is much smaller on
disk than the system it holds, so the automatic budget does not cover it. Set
SAFEGUARD_UNPACK_MAX_GB to about two and a half times the virtual size of
the disk (48 was used for 20 GiB; 30 was not enough) and allow that much
temporary space:
export SAFEGUARD_UNPACK_MAX_GB=48
safeguard sbom --dir appliance.ova --sbom-format bothA value you set in SAFEGUARD_UNPACK_MAX_GB or
SAFEGUARD_UNPACK_TIMEOUT_MINUTES is always used as it is. On a CLI older
than the November 2026 release that added automatic sizing, set
SAFEGUARD_UNPACK_MAX_GB=30 for a 20 GiB QCOW2 or VMDK image.
When the image is not opened
The scan checks the size budget and the free disk space before it reads the disk. If either is too small, the image is listed as not opened, with the reason and the space it needs, and the scan continues. Raise the setting or free the space, then run it again. The SBOM never comes back empty without a stated reason.
Not covered by these measurements
- Images larger than 20 GiB, and VHD or VHDX at this size.
- x86-64 hosts and slower storage. Expect different times.
- Vulnerability matching time.
safeguard scantakes longer thansafeguard sbomon the same image.