Thanks, Andy! All five entries show vmprofile.vmdisk to be blank. The vcl.sql file that came with the 2.3.2 distribution loads them as either localdisk or networkdisk rather than dedicated or shared. I assigned the appropriate values (replacing localdisk with dedicated and networkdisk with shared) and started a reload successfully. For the record, I am using option 3, network and local disk.
SQL output attached below. At this point I've managed to get to the next step in troubleshooting (looks like the windows firewall is blocking ssh) but that may be due to the scrap vm I last created. Thanks again! jeff From: Andy Kurth <[email protected]> To: [email protected], Date: 08/18/2014 01:19 PM Subject: Re: First Base image on new VCL won't load after capture 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
id profilename imageid resourcepath repositorypath repositoryimagetypeid datastorepath datastoreimagetypeid vmpath virtualswitch0 virtualswitch1 virtualswitch2 virtualswitch3 vmdisk username password eth0generated eth1generated 1 VMware ESXi - local storage 1 NULL NULL 1 datastore1 6 datastore1 Private Public NULL NULL NULL NULL 0 0 2 VMware ESXi - network storage 1 NULL NULL 1 nfs-datastore 6 nfs-datastore Private Public NULL NULL NULL NULL 0 0 3 VMware ESXi - local & network storage 1 NULL NULL 1 nfs-datastore 6 datastore1 Private Public NULL NULL NULL NULL 0 0 4 VMware vCenter 1 /DatacenterName/ClusterName/ResourcePoolName repo-datastore 6 nfs-datastore 6 datastore1 Private Public NULL NULL vcenter-admin vcenter-password 0 0 5 KVM - local storage 1 NULL NULL 7 /var/lib/libvirt/images 7 /var/lib/libvirt/images br0 br1 NULL NULL NULL NULL 0 0
