On Thu, Jun 14, 2012 at 03:01:03PM -0500, Michael Jinks wrote: > > [...] > 2012-06-14 > 14:15:57|25286|3:3|image|Module.pm:create_mn_os_object(335)|management > node OS object has already been created, address: 3fc9dc8, returning 1 > 2012-06-14 > > 14:15:57|25286|3:3|image|Module.pm:new(200)|VCL::Module::Provisioning::VMware::VIM_SSH > object created for computer vcl-linux-template-1, address: 432a330 > 2012-06-14 14:15:57|25286|3:3|image|VIM_SSH.pm:initialize(126)|VIM > executable is not available on the VM host, output: > |25286|3:3|image| bash: vim-cmd: command not found > |25286|3:3|image| bash: vmware-vim-cmd: command not found > [...]
There were two problems here. One was that I hadn't finised the steps in the "further steps if using VMware" doc, under "Assign a VM to a Virtual Host". The other was that my ESX machine doesn't store VM's under the default path listed in the "VMware ESX - local storage" VM profile. Fixed that, now going to try it again. Bit by bit... -- Michael Jinks :: mji...@uchicago.edu :: 773-469-9688 University of Chicago IT Services
