Tran, just to clarify, you only need to install the vSphere SDK *OR* open up ssh access on the VM host. It is unnecessary to do both.
Either way, though, your image capture is failing because your virtual host isn't properly configured. Specifically, you don't have a Repository Path defined, but there may be other issues with the VM host configuration. More information is here: https://cwiki.apache.org/confluence/display/VCL/VCL+2.3+-+Further+Steps+if+Using+VMware If you look at the vcld logs, you can usually find clues about error wherever you see "WARNING" markers like this: > |27151|5:5|image| ---- WARNING ---- > |27151|5:5|image| 2012-10-23 > 15:33:30|27151|5:5|image|vcld:warning_handler(613)|Use of uninitialized value > $vmhost_profile_resource_path in pattern match (m//) at > /usr/local/vcl/bin/../lib/VCL/Module/Provisioning/VMware/vSphere_SDK.pm line > 2833. > |27151|5:5|image| ( 0) vcld, warning_handler (line: 613) > |27151|5:5|image| (-1) vSphere_SDK.pm, _get_resource_pool_view (line: 2833) > |27151|5:5|image| (-2) vSphere_SDK.pm, _get_datacenter_view (line: 2632) > |27151|5:5|image| (-3) vSphere_SDK.pm, _get_datastore_info (line: 3242) > |27151|5:5|image| (-4) VMware.pm, get_datastore_info (line: 6740) > |27151|5:5|image| (-5) VMware.pm, _get_datastore_name (line: 7043) The above warning indicates that $vmhost_profile_resource_path was not initialized. To fix this, you can go to the Manage VM Hosts -> VM Host Profile section of the web front-end and define a value for the "Resource Path". Aaron -- Aaron Coburn Systems Administrator and Programmer Academic Technology Services, Amherst College [email protected] On Oct 23, 2012, at 4:47 AM, Tran Vu <[email protected]> wrote: > Hi everyone! > > So as i mentioned before i couldnt capture the image, then i followed your > advises like check the ssh to the host, install vmware vshpere sdk, i also > make sure that i can ssh to the guest vm that i'm going to capture, that's > all checked, > but still i couldnt get it done ,is there anything else that i should check? > here is the log after the capture process failed >
