Re: Reservation Error:

2010-03-18 Thread Andy Kurth
376 |16651|5:5|new| WARNING ^M 377 |16651|5:5|new| 2010-03-17 13:02:45|16651|5:5|new|DataStructure.pm:_automethod(675)|corresponding data has not been initialized for get_computer_preferredimage_id: $self->request_data->{reservation}{5}{computer}{preferredimage}{id}^M

RE: Reservation Error:

2010-03-18 Thread Kumar, Amit H.
the help ... I will give image capture a try first. Amit > -Original Message- > From: Andy Kurth [mailto:andy_ku...@ncsu.edu] > Sent: Thursday, March 18, 2010 10:56 AM > To: vcl-dev@incubator.apache.org > Subject: Re: Reservation Error: > > > 376 |16651|5:5|new| --

Re: Reservation Error:

2010-03-18 Thread Andy Kurth
Yes, the management node needs to be be able to SSH to the VM hosts before attempting the image capture, or any other VM operations. Assuming password authentication is still enabled on the VM hosts, you can run "gen-node-key.sh " for each of them. I wouldn't try the VCL image capture process

RE: Reservation Error:

2010-03-19 Thread Kumar, Amit H.
lumes/15a5e041-86bf33de/golden [r...@colbert vcl-debug]# /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x 128.82.128.252 'ls -1 /vmfs/volumes/15a5e041-86bf33de/golden/' <- Note forward slash thrash vmwarewinxp-base7-v0 Thank you, Amit > -Original Message- > From: Andy K

RE: Reservation Error:

2010-03-22 Thread Kumar, Amit H.
Hi Andy, I followed through every step in esx.README and still not successful in capturing an image: I can SSH to the hypervisor and the VMhost through the management node with the/etc/vcl/vcl.key etc etc ..everything else looks okay; below I also have the query's that I used to create this im

Re: Reservation Error:

2010-03-22 Thread Ryan Johnson
I ran into this as well using the free version of Esxi, I'm not sure what version you are using. It has to do with the exit status returned from the Esx server. Try running the ssh command that VCL runs from the command line, but add the -v option to print out more information. The work-around I

RE: Reservation Error:

2010-03-22 Thread Kumar, Amit H.
Original Message- > From: Ryan Johnson [mailto:rjoh...@gwmail.gwu.edu] > Sent: Monday, March 22, 2010 3:55 PM > To: vcl-dev@incubator.apache.org > Subject: Re: Reservation Error: > > I ran into this as well using the free version of Esxi, I'm not sure what > version you are

Re: Reservation Error:

2010-03-22 Thread Ryan Johnson
t; -Original Message- > > From: Ryan Johnson [mailto:rjoh...@gwmail.gwu.edu] > > Sent: Monday, March 22, 2010 3:55 PM > > To: vcl-dev@incubator.apache.org > > Subject: Re: Reservation Error: > > > > I ran into this as well using the free version of Esxi,

RE: Reservation Error:

2010-03-22 Thread Kumar, Amit H.
Hi Ryan, you are great! I made quite a bit of progress with your suggestion. I hope you can help me with this next step error: Seems like image creation was successful but upon realod/poweron VMware perl toolkit looks for server '128' instead of the full ip. Something seems to be missing: Hope

RE: Reservation Error:

2010-03-23 Thread Kumar, Amit H.
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(64

Re: Reservation Error:

2010-03-23 Thread Ryan Johnson
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

RE: Reservation Error:

2010-03-23 Thread Kumar, Amit H.
ed 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: vcl-dev@incubator.apache.org > Subject: Re: Reser