Re: Reg: Getting an SSH error when trying to make a reservation

2010-04-06 Thread Kiran N
Thanks Aaron!
Please find the file below:

#!/usr/bin/vmware
config.version = "8"
virtualHW.version = "4"
floppy0.present = "false"
nvram = "Windows 2003 R2 EE.nvram"
deploymentPlatform = "windows"
virtualHW.productCompatibility = "hosted"
tools.upgrade.policy = "manual"
powerType.powerOff = "default"
powerType.powerOn = "default"
powerType.suspend = "default"
powerType.reset = "default"

displayName = "Windows 2003 R2 EE"
extendedConfigFile = "Windows 2003 R2 EE.vmxf"

scsi0.present = "true"
scsi0.sharedBus = "none"
scsi0.virtualDev = "lsilogic"
memsize = "4096"
scsi0:0.present = "true"
scsi0:0.fileName = "Windows 2003 R2 EE-01.vmdk"
scsi0:0.deviceType = "scsi-hardDisk"
ide0:0.present = "true"
ide0:0.fileName = "/dev/scd0"
ide0:0.deviceType = "atapi-cdrom"
ide0:0.startConnected = "false"
ethernet0.present = "true"
ethernet0.wakeOnPcktRcv = "false"
ethernet0.networkName = "VM_Access"
ethernet0.addressType = "generated"
guestOSAltName = "Microsoft Windows Server 2003, Enterprise Edition
(32-bit)"
guestOS = "winnetenterprise"
uuid.location = "56 4d b0 02 f8 06 24 bf-2c 97 80 6c 8c 0e 37 24"
uuid.bios = "56 4d b0 02 f8 06 24 bf-2c 97 80 6c 8c 0e 37 24"
snapshot.action = "keep"
sched.cpu.min = "0"
sched.cpu.units = "mhz"
sched.cpu.shares = "normal"
sched.mem.minsize = "0"
sched.mem.shares = "normal"
toolScripts.afterPowerOn = "true"
toolScripts.afterResume = "true"
toolScripts.beforeSuspend = "true"
toolScripts.beforePowerOff = "true"


evcCompatibilityMode = "FALSE"
guestCPUID.0 = "000168747541444d416369746e65"
guestCPUID.1 = "00040f1208002001078bbbff"
guestCPUID.8001 = "00040f1203530009ebd3fbff"
hostCPUID.0 = "000168747541444d416369746e65"
hostCPUID.1 = "00040f12000208002001178bfbff"
hostCPUID.8001 = "00040f120353001febd3fbff"
sched.swap.derivedName =
"/vmfs/volumes/4a54aa4b-88146930-8e6f-00145e6d6a04/Windows 2003 R2
EE/Windows 2003 R2 EE-3bd65d97.vswp"
scsi0:0.redo = ""
userCPUID.0 = "000168747541444d416369746e65"
userCPUID.1 = "00040f12000208002001078bbbff"
userCPUID.8001 = "00040f1203530009ebd3fbff"
vmware.tools.requiredversion = "7303"

ethernet0.generatedAddress = "00:0c:29:0e:37:24"
tools.syncTime = "false"
ethernet0.generatedAddressOffset = "0"

ethernet1.present = "true"
ethernet1.networkName = "VCL VM Private Net Access"
ethernet1.addressType = "generated"

ethernet1.generatedAddress = "00:0c:29:0e:37:2e"
ethernet1.generatedAddressOffset = "10"


On Tue, Apr 6, 2010 at 3:27 PM, Aaron Peeler  wrote:

> 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?
>
> Aaron
>
>
>
> On 4/6/10 3:13 PM, Kiran N wrote:
>
>> Hello,
>> 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
>> unexpectedly.
>>
>> Please check the vcld log file below and let me know if anyone has a
>> solution for this error.
>> Thanks in advance..!
>> Kiran
>>
>> 2010-04-06 13:57:34|19162|31:31|reload|utils.pm:run_ssh_command(6259)|SSH
>> command executed on cleesx.democentral.ibm.com, command:
>> |19162|31:31|reload| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x
>> cleesx.democentral.ibm.com 'vmware-cmd
>> /vmfs/volumes/VCL/esx3-win2003-v0vcl01/esx3-win2003-v0vcl01.vmx getstate'
>> 2>&1
>> |19162|31:31|reload| returning (11, "VMControl error -11: No such v...")
>> 2010-04-06 13:57:34|19162|31:31|reload|vmware.pm:
>> node_status(1914)|VMControl
>> error -11: No such virtual machine
>> 2010-04-06 13:57:34|19162|31:31|reload|vmware.pm:node_status(1925)|vcl01
>> vmstate reports 0
>> 2010-04-06 13:57:34|19162|31:31|reload|vmware.pm:
>> node_status(1963)|returning
>> node status hash reference ($node_status->{status}=RELOAD)
>> 2010-04-06 13:57:34|19162|31:31|reload|new.pm:
>> reload_image(529)|node_status
>> returned a hash reference
>> 2010-04-06 13:57:34|19162|31:31|reload|new.pm:
>> reload_image(534)|node_status
>> hash reference contains key {status}=RELOAD
>>
>>
>>
>
> --
>
> Aaron Peeler
> Program Manager
> Virtual Computing Lab
> NC State University
> aaron_pee...@ncsu.edu
> 919-513-4571
>
>


Re: Reg: Getting an SSH error when trying to make a reservation

2010-04-06 Thread Aaron Peeler

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?

Aaron


On 4/6/10 3:13 PM, Kiran N wrote:

Hello,
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
unexpectedly.

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

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

   


--

Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University
aaron_pee...@ncsu.edu
919-513-4571



Re: Reg: Getting an SSH error when trying to make a reservation

2010-04-06 Thread Kiran N
Hello,
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
unexpectedly.

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

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

|19162|31:31|reload|  WARNING 
|19162|31:31|reload| 2010-04-06
13:57:34|19162|31:31|reload|vcld:warning_handler(636)|Use of uninitialized
value in string eq at /usr/local/vcl/bin/../lib/VCL/new.pm line 573.
|19162|31:31|reload| ( 0) utils.pm, notify (line: 727)
|19162|31:31|reload| (-1) vcld, warning_handler (line: 636)
|19162|31:31|reload| (-2) new.pm, reload_image (line: 573)
|19162|31:31|reload| (-3) new.pm, process (line: 266)
|19162|31:31|reload| (-4) vcld, make_new_child (line: 594)
|19162|31:31|reload| (-5) vcld, main (line: 341)

2010-04-06 13:57:34|19162|31:31|reload|new.pm:reload_image(602)|node status
is RELOAD, vcl01 will be reloaded
2010-04-06 13:57:34|19162|31:31|reload|utils.pm:insertloadlog(4700)|inserted
computer=2, loadimageblade, vcl01 must be reloaded with esx3-win2003-v0
2010-04-06 13:57:34|19162|31:31|reload|new.pm:reload_image(616)|calling
VCL::Module::Provisioning::vmware->does_image_exist()
2010-04-06 13:57:34|19162|31:31|reload|vmware.pm:does_image_exist(2002)|image
repository path: /install/vmware_images
2010-04-06 13:57:34|19162|31:31|reload|utils.pm:run_command(9718)|executed
command: du -c /install/vmware_images/*esx3-win2003-v0* 2>&1 | grep total
2>&1, pid: 19168, exit status: 0, output:
|19162|31:31|reload| 28731484 total
2010-04-06 
13:57:34|19162|31:31|reload|vmware.pm:does_image_exist(2054)|esx3-win2003-v0
exists in /install/vmware_images, size: 28058 MB
2010-04-06 13:57:34|19162|31:31|reload|new.pm:reload_image(619)|esx3-win2003-v0
exists on this management node
2010-04-06 13:57:34|19162|31:31|reload|utils.pm:insertloadlog(4700)|inserted
computer=2, doesimageexists, confirmed image exists
2010-04-06 
13:57:34|19162|31:31|reload|utils.pm:update_computer_state(2218)|computer
2 state updated to: reloading
2010-04-06 13:57:34|19162|31:31|reload|new.pm:reload_image(652)|computer
vcl01 state set to reloading
2010-04-06 13:57:34|19162|31:31|reload|utils.pm:insertloadlog(4700)|inserted
computer=2, info, computer state updated to reloading
2010-04-06 13:57:34|19162|31:31|reload|new.pm:reload_image(663)|calling
VCL::Module::Provisioning::vmware->load() subroutine
2010-04-06 13:57:34|19162|31:31|reload|utils.pm:insertloadlog(4700)|inserted
computer=2, info, calling VCL::Module::Provisioning::vmware->load()
subroutine
2010-04-06 13:57:34|19162|31:31|reload|vmware.pm:control_VM(1510)|control
remove is defined
2010-04-06 13:57:34|19162|31:31|reload|vmware.pm:control_VM(1574)|checking
for base image on cleesx /vmfs/volumes/VCL
2010-04-06 13:57:34|19162|31:31|reload|utils.pm:run_ssh_command(6167)|executing
SSH command on cleesx:
|19162|31:31|reload| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x
cleesx 'ls -1 /vmfs/volumes/VCL' 2>&1
2010-04-06 
13:57:34|19162|31:31|reload|utils.pm:run_ssh_command(6249)|run_ssh_command
output:
|19162|31:31|reload| esx3-win2003-v0
2010-04-06 13:57:34|19162|31:31|reload|utils.pm:run_ssh_command(6263)|SSH
command executed on cleesx, returning (0, "esx3-win2003-v0")
2010-04-06 13:57:34|19162|31:31|reload|vmware.pm:
control_VM(1580)|esx3-win2003-v0
2010-04-06 
13:57:34|19162|31:31|reload|vmware.pm:control_VM(1602)|/vmfs/volumes/VCL/noimagevcl01/noimagevcl01.vmx
directory structure for noimagevcl01 did not exist
2010-04-06 13:57:34|19162|31:31|reload|utils.pm:run_ssh_command(6167)|executing
SSH command on cleesx:
|19162|31:31|reload| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x
cleesx 'vmware-cmd -l' 2>&1
2010-04-06 
13:57:35|19162|31:31|reload|utils.pm:run_ssh_command(6249)|run_ssh_command
output:
|19162|31:31|reload|
/vmfs/volumes/4a54aa4b-88146930-8e6f-00145e6d6a04/Windows 2003 R2 EE/Windows
2003 R2 EE.vmx
2010-04-06 13:57:35|19162|31:31|reload|utils.p

Re: Reg: Getting an SSH error when trying to make a reservation

2010-04-06 Thread Kiran N
Thanks Ryan!
The exact command that I used is:
 /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x cleesx 'ls -1
10.0.0.2:/vcl-nfs/export/golden'
2>&1
And as you said it failed with 'Host Key verification failed' messsage.
i will check the authorized_keys file and will let you know the result.

Thanks,
Kiran

On Tue, Apr 6, 2010 at 1:00 PM, Ryan Johnson  wrote:

> What is the exact syntax of the command you used from the command line?
>  Try
> ssh again but give vcl.key as the -i (identity key) option and I think you
> will get host key verification failed.  I am guessing the problem is that
> the vcl public key is not in the authorized_keys file of the esx box.
>
> On Tue, Apr 6, 2010 at 11:39 AM, Kiran N 
> wrote:
>
> > vcld.log has been attached in this email..!!
> >
> >
> > On Tue, Apr 6, 2010 at 11:37 AM, Kiran N  >wrote:
> >
> >> Hello All,
> >> I am trying to make a reservation for an Windows203 image using ESX
> >> provisioning.
> >> I am facing an SSH error (as seen in the log file) with error code of
> 255.
> >>
> >> The IDENTITY *  lines in the /etc/vcl/vcld.conf are :
> >> IDENTITY_blade_linux=/etc/vcl/vcl.key
> >> IDENTITY_solaris_lab=/etc/vcl/vcl.key
> >> IDENTITY_linux_lab=/etc/vcl/vcl.key
> >> IDENTITY_blade_win=/etc/vcl/vcl.key
> >>
> >> I am using NFS as my datastore. In my vmprofile table I have set the 2
> >> important fields as below:
> >> datastorepath: 10.0.0.2:/vcl-nfs/export/golden  this is the path on
> >> the management node from where vmhost has mounted the image.
> >> vmpath: /vmfs/volumes/VCL  --- This is path on my vmhost machine for the
> >> image.
> >> Also, when I try to ssh into my vmhost machine - cleesx(10.0.0.3)  from
> >> command line on management node, then it does login into it
> successfully.
> >>
> >> The vcld.log file has been attached with this email.
> >> Please provide me with some inputs!
> >>
> >> --
> >> Thanks,
> >> Kiranmye N
> >> WSTI Intern
> >>
> >
> >
> >
> >
> >
>


Re: Reg: Getting an SSH error when trying to make a reservation

2010-04-06 Thread Ryan Johnson
What is the exact syntax of the command you used from the command line?  Try
ssh again but give vcl.key as the -i (identity key) option and I think you
will get host key verification failed.  I am guessing the problem is that
the vcl public key is not in the authorized_keys file of the esx box.

On Tue, Apr 6, 2010 at 11:39 AM, Kiran N  wrote:

> vcld.log has been attached in this email..!!
>
>
> On Tue, Apr 6, 2010 at 11:37 AM, Kiran N wrote:
>
>> Hello All,
>> I am trying to make a reservation for an Windows203 image using ESX
>> provisioning.
>> I am facing an SSH error (as seen in the log file) with error code of 255.
>>
>> The IDENTITY *  lines in the /etc/vcl/vcld.conf are :
>> IDENTITY_blade_linux=/etc/vcl/vcl.key
>> IDENTITY_solaris_lab=/etc/vcl/vcl.key
>> IDENTITY_linux_lab=/etc/vcl/vcl.key
>> IDENTITY_blade_win=/etc/vcl/vcl.key
>>
>> I am using NFS as my datastore. In my vmprofile table I have set the 2
>> important fields as below:
>> datastorepath: 10.0.0.2:/vcl-nfs/export/golden  this is the path on
>> the management node from where vmhost has mounted the image.
>> vmpath: /vmfs/volumes/VCL  --- This is path on my vmhost machine for the
>> image.
>> Also, when I try to ssh into my vmhost machine - cleesx(10.0.0.3)  from
>> command line on management node, then it does login into it successfully.
>>
>> The vcld.log file has been attached with this email.
>> Please provide me with some inputs!
>>
>> --
>> Thanks,
>> Kiranmye N
>> WSTI Intern
>>
>
>
>
>
>


Re: Reg: Getting an SSH error when trying to make a reservation

2010-04-06 Thread Kiran N
vcld.log has been attached in this email..!!

On Tue, Apr 6, 2010 at 11:37 AM, Kiran N  wrote:

> Hello All,
> I am trying to make a reservation for an Windows203 image using ESX
> provisioning.
> I am facing an SSH error (as seen in the log file) with error code of 255.
>
> The IDENTITY *  lines in the /etc/vcl/vcld.conf are :
> IDENTITY_blade_linux=/etc/vcl/vcl.key
> IDENTITY_solaris_lab=/etc/vcl/vcl.key
> IDENTITY_linux_lab=/etc/vcl/vcl.key
> IDENTITY_blade_win=/etc/vcl/vcl.key
>
> I am using NFS as my datastore. In my vmprofile table I have set the 2
> important fields as below:
> datastorepath: 10.0.0.2:/vcl-nfs/export/golden  this is the path on
> the management node from where vmhost has mounted the image.
> vmpath: /vmfs/volumes/VCL  --- This is path on my vmhost machine for the
> image.
> Also, when I try to ssh into my vmhost machine - cleesx(10.0.0.3)  from
> command line on management node, then it does login into it successfully.
>
> The vcld.log file has been attached with this email.
> Please provide me with some inputs!
>
> --
> Thanks,
> Kiranmye N
> WSTI Intern
>
|16143|23:23|reload|  WARNING 
|16143|23:23|reload| 2010-04-05 
11:22:12|16143|23:23|reload|vcld:warning_handler(636)|Use of uninitialized 
value in pattern match (m//) at /usr/local/vcl/bin/../lib/VCL/Module/State.pm 
line 312.
|16143|23:23|reload| ( 0) utils.pm, notify (line: 727)
|16143|23:23|reload| (-1) vcld, warning_handler (line: 636)
|16143|23:23|reload| (-2) State.pm, reservation_failed (line: 312)
|16143|23:23|reload| (-3) new.pm, process (line: 316)
|16143|23:23|reload| (-4) vcld, make_new_child (line: 594)
|16143|23:23|reload| (-5) vcld, main (line: 341)

2010-04-05 
11:22:12|16143|23:23|reload|utils.pm:update_computer_state(2218)|computer 2 
state updated to: failed
2010-04-05 
11:22:12|16143|23:23|reload|State.pm:reservation_failed(312)|computer vcl01 (2) 
state set to failed
2010-04-05 
11:22:12|16143|23:23|reload|utils.pm:update_request_state(2176)|request 23 
state updated to: failed, laststate to: reload
2010-04-05 11:22:12|16143|23:23|reload|State.pm:reservation_failed(325)|set 
request state to 'failed'/'reload'
2010-04-05 11:22:12|16143|23:23|reload|utils.pm:is_inblockrequest(6953)|zero 
rows were returned from database select
2010-04-05 11:22:12|16143|23:23|reload|State.pm:reservation_failed(343)|vcl01 
is NOT in blockcomputers table
2010-04-05 11:22:12|16143|23:23|reload|State.pm:reservation_failed(346)|exiting 
1
2010-04-05 11:22:12|16143|23:23|reload|State.pm:DESTROY(905)|destructor called, 
ref($self)=VCL::new
2010-04-05 
11:22:12|16143|23:23|reload|utils.pm:delete_computerloadlog_reservation(7532)|removing
 computerloadlog entries matching loadstate = begin
2010-04-05 
11:22:12|16143|23:23|reload|utils.pm:delete_computerloadlog_reservation(7579)|deleted
 rows from computerloadlog for reservation id=23
2010-04-05 11:22:12|16143|23:23|reload|State.pm:DESTROY(912)|removed 
computerloadlog rows with loadstate=begin for reservation
2010-04-05 11:22:12|16143|23:23|reload|State.pm:DESTROY(924)|number of database 
handles state process created: 1
2010-04-05 11:22:12|16143|23:23|reload|State.pm:DESTROY(933)|process has a 
database handle stored in $ENV{dbh}, attempting disconnect
2010-04-05 11:22:12|16143|23:23|reload|State.pm:DESTROY(935)|$ENV{dbh}: 
database disconnect successful
2010-04-05 11:22:12|16143|23:23|reload|State.pm:DESTROY(949)|VCL::new process 
16143 exiting
2010-04-05 11:22:12|11472|vcld:REAPER(744)|VCL process exited for reservation 23
2010-04-05 11:22:12|11472|vcld:main(165)|lastcheckin time updated for 
management node 1: 2010-04-05 11:22:12
2010-04-05 11:22:12|11472|23:23|failed|vcld:main(250)|request deleted
2010-04-05 11:22:17|11472|vcld:main(165)|lastcheckin time updated for 
management node 1: 2010-04-05 11:22:17
2010-04-05 11:22:22|11472|vcld:main(165)|lastcheckin time updated for 
management node 1: 2010-04-05 11:22:22
2010-04-05 11:22:27|11472|vcld:main(165)|lastcheckin time updated for 
management node 1: 2010-04-05 11:22:27
2010-04-05 11:22:32|11472|vcld:main(165)|lastcheckin time updated for 
management node 1: 2010-04-05 11:22:32
2010-04-05 11:22:37|11472|vcld:main(165)|lastcheckin time updated for 
management node 1: 2010-04-05 11:22:37
2010-04-05 11:22:42|11472|vcld:main(165)|lastcheckin time updated for 
management node 1: 2010-04-05 11:22:42
2010-04-05 11:22:47|11472|vcld:main(165)|lastcheckin time updated for 
management node 1: 2010-04-05 11:22:47
2010-04-05 11:22:52|11472|vcld:main(165)|lastcheckin time updated for 
management node 1: 2010-04-05 11:22:52
2010-04-05 11:22:57|11472|vcld:main(165)|lastcheckin time updated for 
management node 1: 2010-04-05 11:22:57

[r...@vclrhel01 ~]# tail -f /var/log/vcld.log
2010-04-05 
11:24:22|16380|24:24|reload|utils.pm:get_management_node_id(9345)|environment 
variable: 1
2010-04-05 11:24:22|16380|24:24|reload|new.pm:reload_image(514)|calling 
VCL::Module::Provisioning::vmware->node_status()
2010-04-05 11:24:22|16380|24:24|re

Reg: Getting an SSH error when trying to make a reservation

2010-04-06 Thread Kiran N
Hello All,
I am trying to make a reservation for an Windows203 image using ESX
provisioning.
I am facing an SSH error (as seen in the log file) with error code of 255.

The IDENTITY *  lines in the /etc/vcl/vcld.conf are :
IDENTITY_blade_linux=/etc/vcl/vcl.key
IDENTITY_solaris_lab=/etc/vcl/vcl.key
IDENTITY_linux_lab=/etc/vcl/vcl.key
IDENTITY_blade_win=/etc/vcl/vcl.key

I am using NFS as my datastore. In my vmprofile table I have set the 2
important fields as below:
datastorepath: 10.0.0.2:/vcl-nfs/export/golden  this is the path on the
management node from where vmhost has mounted the image.
vmpath: /vmfs/volumes/VCL  --- This is path on my vmhost machine for the
image.
Also, when I try to ssh into my vmhost machine - cleesx(10.0.0.3)  from
command line on management node, then it does login into it successfully.

The vcld.log file has been attached with this email.
Please provide me with some inputs!

-- 
Thanks,
Kiranmye N
WSTI Intern