VMware Cloud Community
zenking
Hot Shot
Hot Shot
Jump to solution

Error while upgrading VCSA 5.5 to 6.0

I got this error during my vcsa upgrade:

Failed to extend swap file from 0 KB to 16777216 KB

vim.fault.InvalidState

Logs can be found ...

Looks like the VM got created, but can't power on because there wasn't enough disk space for the mem allocation. Kind of aggravating because I only have 6 hosts and 110 VMs, so I chose the Small size db (Tiny didn't even show up as an option). Small allegedly only requires 150 GB of disk space, but I had to bump the new datastore up to 170 before I could choose it for the new vcenter.

I just bumped the DS up to 190 GB. I guess I need to delete the new vm from inventory and try again. Gotta say, the documentation for this upgrade has not been my friend.

VMWare Environment: vSphere 7.0, EQ PS6210 SANs, Dell R730 Hosts, dedicated Dell switches w/ separate vlans for vmotion and iscsi.
Tags (2)
1 Solution

Accepted Solutions
rcporto
Leadership
Leadership
Jump to solution

Login directly on host where you have your vCSA virtual machine and configure the memory reservation to the size of RAM of the vCSA, this way when you power on the virtual machine you will don't need free space to the vswp file. But take in mind that you will still need to free space to grant room for some operations like snapshot.

This KB explain your problem: VMware KB: A virtual machine fails to power on with the error: Failed to extend swap file from 0 KB ...

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto

View solution in original post

3 Replies
zenking
Hot Shot
Hot Shot
Jump to solution

The original vcenter had not gotten to the point where it shut down because the new vm couldn't even power on to receive migration info, so I removed the new vm and deleted from disk. Logging into the old vcenter, everything looks OK. Is there anything else I should check before trying the upgrade again?

Thanks.

VMWare Environment: vSphere 7.0, EQ PS6210 SANs, Dell R730 Hosts, dedicated Dell switches w/ separate vlans for vmotion and iscsi.
0 Kudos
rcporto
Leadership
Leadership
Jump to solution

Login directly on host where you have your vCSA virtual machine and configure the memory reservation to the size of RAM of the vCSA, this way when you power on the virtual machine you will don't need free space to the vswp file. But take in mind that you will still need to free space to grant room for some operations like snapshot.

This KB explain your problem: VMware KB: A virtual machine fails to power on with the error: Failed to extend swap file from 0 KB ...

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
zenking
Hot Shot
Hot Shot
Jump to solution

Thanks, Richardson. I just added disk space and was able to upgrade after that. Also got VUM and client upgraded, but trying to get the VUM plug-in. I'll start a new thread for that.

VMWare Environment: vSphere 7.0, EQ PS6210 SANs, Dell R730 Hosts, dedicated Dell switches w/ separate vlans for vmotion and iscsi.
0 Kudos