'Could not power on VM : No space left on device' when trying to start the Virtual appliance - AM
Originally Published: 2014-09-02
Article Number
Applies To
VMWare ESX
Issue
Failed to power on VM.
Could not power on VM : No space left on device.
Failed to extend swap file from 0k to 8388608 KB.
From AM-28450 , here is a formula to figure the minimum disk space in the LUN before starting the deployment:
Minimum Total disk space = 104 GB +
(GB of memory allocated to the virtual appliance x 2) +
(Number of future snapshots x GB of memory allocated to the virtual appliance)
Cause
105GB main disk
4GB additional disk
1GB for small files
However, to start the appliance, you also need additional space equivalent to the RAM for a swap file 8.4Gb in the default 8GB configuration.
If you may want to make a snapshot in the future, you also need additional space equivalent to the RAM for EACH snapshot you may make.
Related Articles
DLP - the feature you are trying to use is on network resource that is unavailable Number of Views Invalid argument(s) error when trying to change password or PIN on the Authentication Manager 8.1 Self-Service Console Number of Views Why am I being prompted for a SecurID OTP when trying to view the My Authenticators page? Number of Views Defect: VM: HBOS: error occurs when trying to edit HTTP status sources Number of Views Configure Initial Network Settings Using the Identity Router VM Console Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?
