VMware deadlock

Question

I had to temporarily downgrade my computer and I can't get a suspended wmware VM running.

The VM can't be started as there are fewer processors than required in the settings.
The settings can't be changed since the VM is not shut down.
The VM can't be shut down, 'cause it can't be started.

Is there a way around it?

^{In case it matters, I'm running vmware player 4.0.2 build-591240 on Ubuntu 11.10.}

^{Moving the VM temporarily to a better computer is not an option (the overhead is too high and I'm expecting new hardware soon).}

Could it start again once the number of processors has been corrected? — music2myear, Jan 31 '12 at 22:19
I hope so.... at least this is the thing it complains about now. IIRC, I could change such settings at will. — maaartinus, Jan 31 '12 at 22:26

score 2 · Accepted Answer · edited Jan 31 '12 at 22:51

2

You can delete the <machine>.vmss file located in your virtual machine's storage directory and it will be as if you cut power and should be able to start/alter settings.

edited Jan 31 '12 at 22:51

the-wabbit

40,737
13
111
174

answered Jan 31 '12 at 22:35

JamesRyan

8,166
2
25
36

Data loss will occur if files/databases were not saved before suspending. But this should get you up and running. – xeon Jan 31 '12 at 22:55

VMware deadlock

1 Answers1