Link to home
Start Free TrialLog in
Avatar of nellie5713
nellie5713

asked on

VMWare Error message

Symptoms
•      Cannot power on a virtual machine
•      Powering on a virtual machine fails
•      You see the error:

An unexpected error was received from the ESX host while powering on VM <VM name>.
Could not power on VM : Reason
Failed to power on VM.
Failed to extend swap file from 0 KB to size KB.
SOLUTION
Avatar of Nick Rhode
Nick Rhode
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of nellie5713
nellie5713

ASKER

Capacity                 Provisioned                Free
[datastore1]      131.00 GB               971.00 MB                130.05 GB

[VMDatastore]    3.64 TB                       5.4 TB                    5.86 GB
Thanks NRhode

I read the URLs below.  They give a workaround to the problem.  I need to find the cause of the problem.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1030719

Resolution or Solution to try:  http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004082
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Text got shifted during the post.  The actual amounts are below:

[datastore1]
Capacity 131 GB
Provisioned 971.00MB
Free 130.05 GB

[VMDatastore]

Capacity 3.64TB
Provisioned 5.4TB
Free 5.86 GB

It is still low but for now the servers are still running after deleting a few snapshots.   The VMDatastore has all of the database, snapshot, logfiles and swap data.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
There is one physical host and 2 VMware servers.  Only one VMware server is having an issue.

For now deleting  a few snapshots have alleviated the issue.   There also seems to be to many vmdk files that have been generated.  Which could be a part of the problem.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Okay,  I will leave this ticket and try the work around.  I am not sure how long the work around will work, since it isn't the solution but just a work around.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
So if I have 6 gig of memory then I should be able to move the swap file to datastore1  which has a little over 130gb then there will be plenty of space for the swap file, correct?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Okay,
I spoke with Dell Computers  virtualization team and this is what they discovered:  I had taken several snapshots over the months which had taken up most of the space.  We deleted the snapshots and recovered the space that they had taken up.  The space went from 5.86 gb to almost 200gb.  Problem resolved.  From now on I will delete snapshots one week after they are taken to eliminate the swap file not having enough space.
I've requested that this question be closed as follows:

Accepted answer: 0 points for nellie5713's comment #a39524330

for the following reason:

Obtained assistance from Dell's virtualization team and they resolved the issue.  Dell had an simpler solution than changing or editing the path of where the swap file is saved.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Sorry.  Didn't mean to step on any toes.  Snapshots were deleted and consolidated.  We did not move any swap files.  I am just happy that the problem has been resolved.  I didn't try your recommendations.  Who knows, I may have to try them in the future.