Could be something wrong with the .vmx file.

My first thought is to check the drive type - ide or scsi. esx doesn't support ide drive types and any new computers added in have hda as the default value in the database schema.

Could you share that portion of the vmx file?


On 4/6/10 3:13 PM, Kiran N wrote:
I resolved the SSH error, but now facing a new issue. By seeing the log I
think that the reservation process is failing in the last due to error :
VMControl error -999: Unknown error: The poweron operation failed

Please check the vcld log file below and let me know if anyone has a
solution for this error.
Thanks in advance..!

2010-04-06 13:57:34|19162|31:31|reload||SSH
command executed on, command:
|19162|31:31|reload| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x 'vmware-cmd
/vmfs/volumes/VCL/esx3-win2003-v0vcl01/esx3-win2003-v0vcl01.vmx getstate'
|19162|31:31|reload| returning (11, "VMControl error -11: No such v...")
2010-04-06 13:57:34|19162|31:31|reload||VMControl
error -11: No such virtual machine
2010-04-06 13:57:34|19162|31:31|reload||vcl01
vmstate reports 0
2010-04-06 13:57:34|19162|31:31|reload||returning
node status hash reference ($node_status->{status}=RELOAD)
2010-04-06 13:57:34|19162|31:31|reload||node_status
returned a hash reference
2010-04-06 13:57:34|19162|31:31|reload||node_status
hash reference contains key {status}=RELOAD


Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University

Reply via email to