Re: Fwd: Image Failing to boot up in VCL 2.2
There may be a more detailed error message if you try to manually power-on the VM from the vSphere Client. Also within the vSphere Client, try editing the settings of the VM. When there's a problem it often displays a more-useful error when you click Edit Settings. If neither of these provide useful information, you can look in the log file generated by VMware for the VM. The following file should exist: /vmfs/volumes/netappfiler02-sata1/vmguest-8_6-v0/vmware.log The info in this file is pretty raw but it sometimes is helpful for troubleshooting. The file grows each time an operation is attempted on the VM. To capture just the output from the power-on error, rename vmware.log to something else and attempt to power-on the VM again. vmware.log should be recreated. Please reply with the contents if the vSphere Client tests don't provide anything useful. -Andy On 3/2/2011 8:48 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm moving this to the vcl-user list. We're trying to separate the vcl-dev lists and vcl-user lists into development and user support. Josh - -- Forwarded Message -- Subject: Image Failing to boot up in VCL 2.2 Date: Tuesday March 01, 2011, 5:48:25 pm From: Alexander Pattersonalexander.patter...@csueastbay.edu To: vcl-...@incubator.apache.org 011-03-01 14:46:33|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 12 (vmsvc/getallvms) 2011-03-01 14:46:33|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclesxi01: vim-cmd vmsvc/getallvms 2011-03-01 14:46:33|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 13 (vmsvc/power.on 304) 2011-03-01 14:46:35|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclesxi01: vim-cmd vmsvc/power.on 304 2011-03-01 14:46:35|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 14 (vmsvc/getallvms) 2011-03-01 14:46:35|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclesxi01: vim-cmd vmsvc/getallvms 2011-03-01 14:46:35|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 15 (vmsvc/get.tasklist 304) 2011-03-01 14:46:36|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclesxi01: vim-cmd vmsvc/get.tasklist 304 2011-03-01 14:46:36|24259|52:44|new|VIM_SSH.pm:_wait_for_task(748)|checking status of task: haTask-304-vim.VirtualMachine.powerOn-90991068 2011-03-01 14:46:36|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 16 (vimsvc/task_info haTask-304-vim.VirtualMachine.powerOn-90991068) 2011-03-01 14:46:36|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclesxi01: vim-cmd vimsvc/task_info haTask-304-vim.VirtualMachine.powerOn-90991068 |24259|52:44|new| WARNING |24259|52:44|new| 2011-03-01 14:46:36|24259|52:44|new|VIM_SSH.pm:_wait_for_task(783)|task haTask-304-vim.VirtualMachine.powerOn-90991068 did not complete successfully, state: error, error message: The task was canceled by a user. |24259|52:44|new| ( 0) VIM_SSH.pm, _wait_for_task (line: 783) |24259|52:44|new| (-1) VIM_SSH.pm, vm_power_on (line: 969) |24259|52:44|new| (-2) VMware.pm, load (line: 407) |24259|52:44|new| (-3) new.pm, reload_image (line: 687) |24259|52:44|new| (-4) new.pm, process (line: 282) |24259|52:44|new| (-5) vcld, make_new_child (line: 568) |24259|52:44|new| WARNING |24259|52:44|new| 2011-03-01 14:46:36|24259|52:44|new|VIM_SSH.pm:vm_power_on(974)|failed to power on VM: /vmfs/volumes/netappfiler02-sata1/vmguest-8_6-v0/vmguest-8_6-v0.vmx, the vim power on task did not complete successfully, vim-cmd vmsvc/power.on 304 output: |24259|52:44|new| Powering on VM: |24259|52:44|new| Power on failed |24259|52:44|new| ( 0) VIM_SSH.pm, vm_power_on (line: 974) |24259|52:44|new| (-1) VMware.pm, load (line: 407) |24259|52:44|new| (-2) new.pm, reload_image (line: 687) |24259|52:44|new| (-3) new.pm, process (line: 282) |24259|52:44|new| (-4) vcld, make_new_child (line: 568) |24259|52:44|new| (-5) vcld, main (line: 346) |24259|52:44|new| WARNING |24259|52:44|new| 2011-03-01 14:46:36|24259|52:44|new|VMware.pm:load(408)|failed to power on VM vmguest-8 on VM host: vclesxi01 |24259|52:44|new| ( 0) VMware.pm, load (line: 408) |24259|52:44|new| (-1) new.pm, reload_image (line: 687) |24259|52:44|new| (-2) new.pm, process (line: 282) |24259|52:44|new| (-3) vcld, make_new_child (line: 568) |24259|52:44|new| (-4) vcld, main (line: 346) |24259|52:44|new| WARNING |24259|52:44|new| 2011-03-01 14:46:36|24259|52:44|new|new.pm:reload_image(692)|vmwarewinxp-build33-v0 failed to load on vmguest-8, returning |24259|52:44|new| ( 0) new.pm, reload_image (line: 692) |24259|52:44|new| (-1) new.pm, process (line: 282) |24259|52:44|new| (-2) vcld, make_new_child (line: 568) |24259|52:44|new| (-3) vcld, main (line: 346) 2011-03-01 14:46:36|24259|52:44|new|utils.pm:insertloadlog(3875)|inserted computer=22, loadimagefailed,
Fwd: Image Failing to boot up in VCL 2.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm moving this to the vcl-user list. We're trying to separate the vcl-dev lists and vcl-user lists into development and user support. Josh - -- Forwarded Message -- Subject: Image Failing to boot up in VCL 2.2 Date: Tuesday March 01, 2011, 5:48:25 pm From: Alexander Patterson alexander.patter...@csueastbay.edu To: vcl-...@incubator.apache.org 011-03-01 14:46:33|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 12 (vmsvc/getallvms) 2011-03-01 14:46:33|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclesxi01: vim-cmd vmsvc/getallvms 2011-03-01 14:46:33|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 13 (vmsvc/power.on 304) 2011-03-01 14:46:35|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclesxi01: vim-cmd vmsvc/power.on 304 2011-03-01 14:46:35|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 14 (vmsvc/getallvms) 2011-03-01 14:46:35|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclesxi01: vim-cmd vmsvc/getallvms 2011-03-01 14:46:35|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 15 (vmsvc/get.tasklist 304) 2011-03-01 14:46:36|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclesxi01: vim-cmd vmsvc/get.tasklist 304 2011-03-01 14:46:36|24259|52:44|new|VIM_SSH.pm:_wait_for_task(748)|checking status of task: haTask-304-vim.VirtualMachine.powerOn-90991068 2011-03-01 14:46:36|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 16 (vimsvc/task_info haTask-304-vim.VirtualMachine.powerOn-90991068) 2011-03-01 14:46:36|24259|52:44|new|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclesxi01: vim-cmd vimsvc/task_info haTask-304-vim.VirtualMachine.powerOn-90991068 |24259|52:44|new| WARNING |24259|52:44|new| 2011-03-01 14:46:36|24259|52:44|new|VIM_SSH.pm:_wait_for_task(783)|task haTask-304-vim.VirtualMachine.powerOn-90991068 did not complete successfully, state: error, error message: The task was canceled by a user. |24259|52:44|new| ( 0) VIM_SSH.pm, _wait_for_task (line: 783) |24259|52:44|new| (-1) VIM_SSH.pm, vm_power_on (line: 969) |24259|52:44|new| (-2) VMware.pm, load (line: 407) |24259|52:44|new| (-3) new.pm, reload_image (line: 687) |24259|52:44|new| (-4) new.pm, process (line: 282) |24259|52:44|new| (-5) vcld, make_new_child (line: 568) |24259|52:44|new| WARNING |24259|52:44|new| 2011-03-01 14:46:36|24259|52:44|new|VIM_SSH.pm:vm_power_on(974)|failed to power on VM: /vmfs/volumes/netappfiler02-sata1/vmguest-8_6-v0/vmguest-8_6-v0.vmx, the vim power on task did not complete successfully, vim-cmd vmsvc/power.on 304 output: |24259|52:44|new| Powering on VM: |24259|52:44|new| Power on failed |24259|52:44|new| ( 0) VIM_SSH.pm, vm_power_on (line: 974) |24259|52:44|new| (-1) VMware.pm, load (line: 407) |24259|52:44|new| (-2) new.pm, reload_image (line: 687) |24259|52:44|new| (-3) new.pm, process (line: 282) |24259|52:44|new| (-4) vcld, make_new_child (line: 568) |24259|52:44|new| (-5) vcld, main (line: 346) |24259|52:44|new| WARNING |24259|52:44|new| 2011-03-01 14:46:36|24259|52:44|new|VMware.pm:load(408)|failed to power on VM vmguest-8 on VM host: vclesxi01 |24259|52:44|new| ( 0) VMware.pm, load (line: 408) |24259|52:44|new| (-1) new.pm, reload_image (line: 687) |24259|52:44|new| (-2) new.pm, process (line: 282) |24259|52:44|new| (-3) vcld, make_new_child (line: 568) |24259|52:44|new| (-4) vcld, main (line: 346) |24259|52:44|new| WARNING |24259|52:44|new| 2011-03-01 14:46:36|24259|52:44|new|new.pm:reload_image(692)|vmwarewinxp-build33-v0 failed to load on vmguest-8, returning |24259|52:44|new| ( 0) new.pm, reload_image (line: 692) |24259|52:44|new| (-1) new.pm, process (line: 282) |24259|52:44|new| (-2) vcld, make_new_child (line: 568) |24259|52:44|new| (-3) vcld, main (line: 346) 2011-03-01 14:46:36|24259|52:44|new|utils.pm:insertloadlog(3875)|inserted computer=22, loadimagefailed, vmwarewinxp-build33-v0 failed to load on vmguest-8 |24259|52:44|new| WARNING |24259|52:44|new| 2011-03-01 14:46:36|24259|52:44|new|new.pm:process(329)|failed to load vmguest-8 with vmwarewinxp-build33-v0 |24259|52:44|new| ( 0) new.pm, process (line: 329) |24259|52:44|new| (-1) vcld, make_new_child (line: 568) |24259|52:44|new| (-2) vcld, main (line: 346) 2011-03-01 14:46:36|24259|52:44|new| DataStructure.pm:get_computer_state_name(2299)|attempting to retrieve current state of computer vmguest-8 from the database 2011-03-01 14:46:36|24259|52:44|new| DataStructure.pm:get_computer_state_name(2330)|retrieved current state of computer vmguest-8 from the database: reloading 2011-03-01 14:46:36|24259|52:44|new|DataStructure.pm:_automethod(835)|data structure updated: $self-request_data-{reservation}{44}{computer}{state}{name} |24259|52:44|new| computer_state_name = reloading 2011-03-01 14:46:36|24259|52:44|new|