Of course, now I am a little confused. Why rely on 
currentimage.txt, when VCL queries the hypervisor not much 
later and can get that same information?

2010-07-12 00:07:34|2568|154:157|new|esx.pm:load(208)|VM info 
command: /opt/vcl/bin/apps/vm/vminfo.pl --server 'vmware2' --
vmname host14 --username vcl --password ##########
2010-07-12 00:07:36|2568|154:157|new|esx.pm:load(211)|VM info 
|2568|154:157|new| Information of Virtual Machine host14
|2568|154:157|new| Name: host14
|2568|154:157|new| No. of CPU(s): 1
|2568|154:157|new| Memory Size: 1024
|2568|154:157|new| Virtual Disks: 1
|2568|154:157|new| Template: 0
|2568|154:157|new| vmPathName: [VCL] 
|2568|154:157|new| Guest OS: Microsoft Windows XP Professional 
|2568|154:157|new| guestId: winXPProGuest
|2568|154:157|new| Host name: vcl-winxp-base.Engineering.soe
|2568|154:157|new| IP Address:
|2568|154:157|new| VMware Tools: VMware Tools is running and 
the version is current
|2568|154:157|new| Cpu usage: 12 MHz
|2568|154:157|new| Host memory usage: 459 MB
|2568|154:157|new| Guest memory usage: 61 MB
|2568|154:157|new| Overall Status: The entity is OK

It would see to me that this could be a secondary validation 
as this step happens right before the power-off command is 

Nevertheless, I will follow your advice and update our images 
to insure the right image name is in currentimage.txt


- Cliff
--- Begin Message ---
On 7/9/10 5:30 PM, Clifton B Wood wrote:
I've been testing our VCL setup and I've noticed something in
the logs.

Recently I loaded an image from VCL and it loaded
successfully. According to the logs, after I ended the
reservation, the system proceeded to unregister and reload
that same image to the same host.

I then tried requesting that exact same image. It selected the
same host I used previously. However, rather than quickly
provision the fresh image, it unregistered and reloaded that
exact same image on the exact same VM.

What am I missing here? The image on the VM was just ready for
a quick post setup. Why the full drop and reload routine?

Relevant log entries can be provided if necessary, but I have
to edit them down, first.

Is the currentimage.txt correct in your image? I've noticed that if VCL loads an image for you, it will not verify the currentimage.txt. However, if there is an image preloaded (as with your second attempt), then it will ssh in and check the contents of the file. If it doesn't match with the image name it expects, it will decide its the wrong image and reimage the host. If this is the case you should see a log message indicating that VCL thinks the wrong image is loaded and that is going to do a reload.
--- End Message ---

Reply via email to