gbw wrote:Whether intended or not, mpack's statement of "The error has nothing to do with the amount of memory allocated to the VM." is incorrect.
Don't misquote (by quoting out of context). In its proper context the statement was that the "VT-x locked or unavailable" error cannot be solved by the explicit solution you offered, of halving the VM RAM allocation from 4GB to 2GB, and my statement is correct. However if you had revealed the crucial info that 4GB was more than your
host had available, then I might have added that the exact point in time at which the startup runs out of memory is basically a crapshoot, and in that case the "or unavailable" part of the error message is the bit that applies.
The fact remains: telling people that halving the VM memory allocation is how you fix the OPs problem
is flat out dead wrong.