by Catrinisin » Wed Dec 05, 2007 6:42 pm
What version of VMWare Server are you using?
I had this error once and I upgraded to VMWare Server 1.0.3 and the problem went away.
FYI, 1.0.4 has other issues with ESVA.
VMWare Server 2.0 is coming out soon, in Beta now.
Also, VMWare ESX server seems to run ESVA really well.