I can't tell from the output if it's failing to determine vmx or vmdk
space. It would be helpful if you change VMware.pm line 2393 to try to
output the values it is checking, change it to:
notify($ERRORS{'WARNING'}, 0, "failed to determine additional bytes
required for the vmx and vmdk directories on VM host $vmhost_name, vmx:
$vmx_additional_bytes_required, vmdk: $vmdk_additional_bytes_required");
This will generate an ugly "failed to concatenate an undefined variable"
warning in vcld.log but at least we will be able to tell which value it is
failing to retrieve, $vmx_additional_bytes_required or
$vmdk_additional_bytes_required.
Also, please include the entire vcld.log output for the entire process.
Some information may have been retrieved earlier on in the execution which
could be helpful for debugging.
-Andy
On Fri, Aug 8, 2014 at 11:33 AM, Jeffrey Kirby <[email protected]>
wrote:
> I've now also added an ESXi 5.1 host and it can't load to that, either,
> same error.
>
> Running vcld with the switch -d doesn't seem to add any debug info to the
> log. Am I missing something?
>
>
>
> From: Jeffrey Kirby <[email protected]>
> To: [email protected],
> Date: 08/06/2014 02:07 PM
> Subject: First Base image on new VCL won't load after capture
> ------------------------------
>
>
>
> I am trying to deploy a new VCL instance. I'm at the point where I have
> captured a windows 8.1 image (64-bit, 64-bit cygwin; I altered Windows.pm
> to correct the location of Sysnative as system32). The problem I'm
> experiencing is that on redeploy at the end of the capture it errored out
> with not being able to determine additional bytes required for the vmx and
> vmdk directories on VM host. I can recreate the issue without capturing by
> just requesting an image reload through Manage Computers > Computer
> Utilities.
>
>
