VCL
  1. VCL
  2. VCL-542

Failed to capture Windows 2008 R2 64-bit server

    Details

    • Type: Question Question
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.2.1
    • Fix Version/s: None
    • Component/s: vcld (backend)
    • Labels:
    • Environment:

      VCL server - Centos 5 32bit - all in one (management node, database, front end)
      Captured system - Windows 2008 R2 64-bit server

      Description

      We have an issue with capturing VMware image of Windows 2008 R2 64-bit server. We have done all prerequisities which are needed by the documentation. Then it run through capturing proces without any error or even warning and freeze for couple of hours on following lines:

      2011-12-01 21:38:10|25442|72:72|image|utils.pm:run_ssh_command(5380)|executing SSH command on vm111:

      25442 72:72 image /usr/bin/ssh -i /etc/vcl/vcl.key -o StrictHostKeyChecking=no -l root -p 22 -x vm111 '/bin/cygstart.exe $SYSTEMROOT/system32/cmd.exe /c "C:/Windows/Sysnative/netsh.exe interface ip set address name=\"Local Area Connection\" source=dhcp & C:/Windows/Sysnative/netsh.exe interface ip set dnsservers name=\"Local Area Connection\" source=dhcp & C:/Windows/Sysnative/netsh.exe interface ip set address name=\"Local Area Connection 2\" source=dhcp & C:/Windows/Sysnative/netsh.exe interface ip set dnsservers name=\"Local Area Connection 2\" source=dhcp & C:/Windows/Sysnative/netsh.exe interface ip reset & C:/Windows/Sysnative/ipconfig.exe /release & C:/Windows/Sysnative/ipconfig.exe /flushdns & C:/Windows/Sysnative/arp.exe -d * & C:/Windows/Sysnative/route.exe DELETE 0.0.0.0 MASK 0.0.0.0 & C:/Windows/Sysnative/shutdown.exe /s /t 0 /f"' 2>&1

      After few hours capturing proces contiues with:

      25442 72:72 image returning (255, "Read from remote host vm111: C...")
      2011-12-01 23:57:09
      25442 72:72 image Windows.pm:shutdown(3567) attempt 1/12: executed shutdown command on vm111
      2011-12-01 23:57:09
      25442 72:72 image Module.pm:code_loop_timeout(742) waiting for vm111 to NOT respond to ping, maximum of 180 seconds
      2011-12-01 23:57:09
      25442 72:72 image Module.pm:code_loop_timeout(759) attempt 1: waiting for vm111 to NOT respond to ping
      2011-12-01 23:57:10
      25442 72:72 image Module.pm:code_loop_timeout(762) waiting for vm111 to NOT respond to ping, code returned true
      2011-12-01 23:57:10
      25442 72:72 image Module.pm:code_loop_timeout(742) waiting for vm111 to power off, maximum of 300 seconds
      2011-12-01 23:57:10
      25442 72:72 image Module.pm:code_loop_timeout(759) attempt 1: waiting for vm111 to power off
      2011-12-01 23:57:10
      25442 72:72 image VIM_SSH.pm:_run_vim_cmd(193) vim-cmd call count: 7 (vmsvc/getallvms)
      2011-12-01 23:57:30
      25442 72:72 image VIM_SSH.pm:_run_vim_cmd(208) executed command on VM host vmhost: vim-cmd vmsvc/getallvms
      2011-12-01 23:57:30
      25442 72:72 image VIM_SSH.pm:_run_vim_cmd(193) vim-cmd call count: 8 (vmsvc/power.getstate 1232)
      2011-12-01 23:57:51
      25442 72:72 image VIM_SSH.pm:_run_vim_cmd(208) executed command on VM host vmhost: vim-cmd vmsvc/power.getstate 1232
      2011-12-01 23:57:51
      25442 72:72 image VIM_SSH.pm:get_vm_power_state(884) vmsvc/power.getstate 1232:
      25442 72:72 image Retrieved runtime info
      25442 72:72 image Powered off

      ....

      After all, base image is created, but its malformed, and every time when it trying to boot up we get bsod with 0x0000007B error
      We try to solve this issue for 3 days and we are out of ideas where we done a mistake.
      Thank for help
      Martin Hátaš

        Activity

        Martin Hátaš created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Martin Hátaš
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development