Hi Ryan, Thank you for your quick response. I just realized the part with giving hostname rather than just the IP for VMhost by looking at the regular expression parsing for hostname. I didn't know that we need to have the same name for Vmguest and the base image. Now that you mentioned it makes sense why the code is looking for vmguest name.
I will give this a try. Thank you!!! Amit > -----Original Message----- > From: Ryan Johnson [mailto:rjoh...@gwmail.gwu.edu] > Sent: Tuesday, March 23, 2010 12:50 PM > To: firstname.lastname@example.org > Subject: Re: Reservation Error: > > I believe when you are creating a base image, the vmguest name should be the > same as the name of the image you are creating it should be in a format like > vmwarewinxp-base7-v1. Note that the vm you are imaging should have this > name as well as the vmdk file. Your other problem with the hostname is that > you need to use the hostname of the esxi server in the hostname column of > the computer table entry you have for your esxi server (rather than the IP > address). Because VCL just uses the hostname and not the fully qualified > name, make sure you have an entry for the hostname in your /etc/hosts file > on the management node. > > On Tue, Mar 23, 2010 at 11:01 AM, Kumar, Amit H. <ahku...@odu.edu> wrote: > > > Hi All, > > > > Looking closely it looks like there is an issue when, the esx.pm picks all > > the parameters to initiate a poweroff command on the VMguest using the > > VMware Perl toolkit API > > > > Please advise ...if my understanding below is right or wrong? > > > > 2010-03-22 16:51:09|15553|2:2|image|esx.pm:capture(646)|found previous > > name= > > 2010-03-22 16:51:09|15553|2:2|image|esx.pm:capture(648)|SSHing to node to > > configure currentimage.txt > > 2010-03-22 16:51:09|15553|2:2|image|utils.pm:run_ssh_command(6180)|executing > > SSH command on resxi000: > > |15553|2:2|image| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x > > resxi000 'echo esx3-basewinxp-v0 > /root/currentimage.txt' 2>&1 > > 2010-03-22 > 16:51:10|15553|2:2|image|utils.pm:run_ssh_command(6262)|run_ssh_command > > output: > > |15553|2:2|image| bash: /root/currentimage.txt: No such file or directory > > 2010-03-22 16:51:10|15553|2:2|image|utils.pm:run_ssh_command(6272)|SSH > > command executed on resxi000, command: > > |15553|2:2|image| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x > > resxi000 'echo esx3-basewinxp-v0 > /root/currentimage.txt' 2>&1 > > |15553|2:2|image| returning (1, "bash: /root/currentimage.txt: ...") > > 2010-03-22 16:51:10|15553|2:2|image|esx.pm:capture(658)|Power off command: > > /usr/lib/vmware-vcli/apps/vm/vmcontrol.pl --server '128' --vmname resxi000 > > --operation poweroff --username 0 --password 'xxxxxxxxxxx' > > > > #>>>> > > 1. Here the server info seems to be wrong. > > 2. --vmname should actually be " esx3-basewinxp-v0" and not the > > VMguest name; > > 3. NOT sure if the username 0 is associated with "root" ??? if > > yes then that seems right. > > > > When I corrected the above info and executed on command line it powered off > > the VMguest. > > > > I am still looking into where the above incorrect info is pulled from so > > that I can correct it. Any idea ?? Any database tables ?? > > I am also curious to know if we are supposed to name our Vmguest based on > > the vmnames? Just for imaging purpose? > > > > Thank you, > > Amit > > > >