'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
Invalid argument(s) error when trying to change password or PIN on the Authentication Manager 8.1 Self-Service Console Number of Views How to Properly Move AM 8.X VM to a new ESX environment Number of Views Error "Warning NTP and VM Host TimeSync should not be enabled at the same time" in RSA Authentication Manager Number of Views Error "Alias name is too long" while trying to assign an alias to a user in RSA Authentication Manager 8.x Number of Views Configure Initial Network Settings Using the Identity Router VM Console Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA Authentication Manager 8.9 Patches and Hotfixes Readme Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
