Sorry for the delay, vacation... I think I may have traced down the problem. The get_image_size_bytes subroutine in VMware.pm is trying to retrieve the value of vmprofile.vmdisk in the database: my $vmprofile_vmdisk = $self->data->get_vmhost_profile_vmdisk() || return;
If it fails to retrieve this value it returns null, unfortunately without generating a warning. When it returns null, the code which called it fails on down the stack. My first guess would be that there is a problem with this value in your database. From the output of the error email you included in a previous message, other places in the code are not able to retrieve this value: reservation failed on vm0401: process failed after trying to load or make > available > ------------------------------------------------------------------------ > time: 2014-08-07 21:31:08 > ... > vm host: node4-vcl > vm host ID: 1 > vm host computer ID: 1 > vm profile: VMware ESXi - local & network storage > vm profile VM path: datastore1 > vm profile repository path: <undefined> > vm profile datastore path: nfs-datastore > vm profile disk type: Normally, the "vm profile disk type" line would display a value. What does your vmprofile table contain? Please dump it via "SELECT * FROM vmprofile;" and send the output. It would be unusual if the problem is due to a null or blank vmprofile.vmdisk value because the default schema does not permit this value to be null, and forces it to either be "shared" or "dedicated". -Andy
