RE: questions regarding creating base images
Aaron, Never mind my previous email. I have figured out the problem. The repository path was set wrong. It works now. Thanks a lot for your help. Lei From: Huang,Lei [lhu...@pvamu.edu] Sent: Friday, October 07, 2011 3:36 PM To: aaron_pee...@ncsu.edu Cc: vcl-user@incubator.apache.org Subject: RE: questions regarding creating base images Aaron, Thanks for the information. I upgraded to VMware server 2.0, but have encountered some other issues. I have restored it to 1.0 now. Yes, I am using VCL 2.2.1. I changed the provision module to 'VMware' and see more progress for the capturing base image. However, it still failed at the end. Can you please see what the problem is this time? Thanks again, Lei = 2011-10-07 15:02:06|624|607:607|image|Module.pm:code_loop_timeout(742)|waiting for vmguest-3 to power off, maximum of 600 seconds 2011-10-07 15:02:06|624|607:607|image|Module.pm:code_loop_timeout(759)|attempt 1: waiting for vmguest-3 to power off 2011-10-07 15:02:06|624|607:607|image|vmware_cmd.pm:get_vm_power_state(242)|power state of VM 'CentOS5_5-base10-v0.vmx': off 2011-10-07 15:02:06|624|607:607|image|Module.pm:code_loop_timeout(762)|waiting for vmguest-3 to power off, code returned true 2011-10-07 15:02:07|624|607:607|image|Linux.pm:file_exists(1404)|'/install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk' exists on CSB303, files: 1, directories: 0, links: 0 2011-10-07 15:02:07|624|607:607|image|Linux.pm:file_exists(1390)|file or directory does not exist on CSB303: '/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk' 2011-10-07 15:02:07|624|607:607|image|VMware.pm:rename_vmdk(5026)|attempting to rename vmdk: '/install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk' --> '/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk' 2011-10-07 15:02:07|624|607:607|image|Linux.pm:create_directory(1520)|directory created on CSB303: '/install/vmware_files/vmwarelinux-MyCentOS357-v0' 2011-10-07 15:02:07|624|607:607|image|VMware.pm:rename_vmdk(5049)|'move_virtual_disk' subroutine has not been implemented by the API: VCL::Module::Provisioning::VMware::vmware_cmd 2011-10-07 15:02:07|624|607:607|image|VMware.pm:rename_vmdk(5056)|attempting to rename vmdk file using vmware-vdiskmanager: /install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk --> /install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk 2011-10-07 15:02:07|624|607:607|image|VMware.pm:rename_vmdk(5063)|renamed vmdk file by executing 'vmware-vdiskmanager' command on VM host: |624|607:607|image| command: vmware-vdiskmanager -n "/install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk" "/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk" |624|607:607|image| output: Using log file /tmp/vmware-root/vdiskmanager.log |624|607:607|image| Renaming completed successfully. 2011-10-07 15:02:07|624|607:607|image|Linux.pm:file_exists(1404)|'/install/vmware_files' exists on CSB303, files: 0, directories: 1, links: 0 2011-10-07 15:02:07|624|607:607|image|VMware.pm:is_repository_mounted_on_vmhost(5485)|image repository is mounted on VM host CSB303: /install/vmware_files 2011-10-07 15:02:07|624|607:607|image|VMware.pm:capture(596)|vmdk will be copied directly from VM host CSB303 to the image repository in the 2gbsparse disk format 2011-10-07 15:02:08|624|607:607|image|VMware.pm:get_vmhost_product_name(5405)|VMware product being used on VM host CSB303: 'VMware Server 1.0.10 build-203137' 2011-10-07 15:02:08|624|607:607|image|Linux.pm:file_exists(1404)|'/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk' exists on CSB303, files: 1, directories: 0, links: 0 2011-10-07 15:02:08|624|607:607|image|Linux.pm:file_exists(1404)|'/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk' exists on CSB303, files: 1, directories: 0, links: 0 |624|607:607|image| WARNING |624|607:607|image| 2011-10-07 15:02:08|624|607:607|image|VMware.pm:copy_vmdk(4781)|destination vmdk file path already exists on VM host CSB303: /install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk |624|607:607|image| ( 0) VMware.pm, copy_vmdk (line: 4781) |624|607:607|image| (-1) VMware.pm, capture (line: 600) |624|607:607|image| (-2) image.pm, process (line: 162) |624|607:607|image| (-3) vcld, make_new_child (line: 568) |624|607:607|image| (-4) vcld, main (line: 346) |624|607:607|image| WARNING |624|607:607|image| 2011-10-07 15:02:08|624|607:607|image|VMware.pm:capture(604)|failed to copy the vmdk files after the VM was powered off: '/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk' --> '/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk' |624|607:607|image| ( 0) VMware.pm, capture (line: 604) |62
RE: questions regarding creating base images
Aaron, Thanks for the information. I upgraded to VMware server 2.0, but have encountered some other issues. I have restored it to 1.0 now. Yes, I am using VCL 2.2.1. I changed the provision module to 'VMware' and see more progress for the capturing base image. However, it still failed at the end. Can you please see what the problem is this time? Thanks again, Lei = 2011-10-07 15:02:06|624|607:607|image|Module.pm:code_loop_timeout(742)|waiting for vmguest-3 to power off, maximum of 600 seconds 2011-10-07 15:02:06|624|607:607|image|Module.pm:code_loop_timeout(759)|attempt 1: waiting for vmguest-3 to power off 2011-10-07 15:02:06|624|607:607|image|vmware_cmd.pm:get_vm_power_state(242)|power state of VM 'CentOS5_5-base10-v0.vmx': off 2011-10-07 15:02:06|624|607:607|image|Module.pm:code_loop_timeout(762)|waiting for vmguest-3 to power off, code returned true 2011-10-07 15:02:07|624|607:607|image|Linux.pm:file_exists(1404)|'/install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk' exists on CSB303, files: 1, directories: 0, links: 0 2011-10-07 15:02:07|624|607:607|image|Linux.pm:file_exists(1390)|file or directory does not exist on CSB303: '/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk' 2011-10-07 15:02:07|624|607:607|image|VMware.pm:rename_vmdk(5026)|attempting to rename vmdk: '/install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk' --> '/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk' 2011-10-07 15:02:07|624|607:607|image|Linux.pm:create_directory(1520)|directory created on CSB303: '/install/vmware_files/vmwarelinux-MyCentOS357-v0' 2011-10-07 15:02:07|624|607:607|image|VMware.pm:rename_vmdk(5049)|'move_virtual_disk' subroutine has not been implemented by the API: VCL::Module::Provisioning::VMware::vmware_cmd 2011-10-07 15:02:07|624|607:607|image|VMware.pm:rename_vmdk(5056)|attempting to rename vmdk file using vmware-vdiskmanager: /install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk --> /install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk 2011-10-07 15:02:07|624|607:607|image|VMware.pm:rename_vmdk(5063)|renamed vmdk file by executing 'vmware-vdiskmanager' command on VM host: |624|607:607|image| command: vmware-vdiskmanager -n "/install/vmware_files/CentOS5_5-base10-v0/CentOS5_5-base10-v0.vmdk" "/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk" |624|607:607|image| output: Using log file /tmp/vmware-root/vdiskmanager.log |624|607:607|image| Renaming completed successfully. 2011-10-07 15:02:07|624|607:607|image|Linux.pm:file_exists(1404)|'/install/vmware_files' exists on CSB303, files: 0, directories: 1, links: 0 2011-10-07 15:02:07|624|607:607|image|VMware.pm:is_repository_mounted_on_vmhost(5485)|image repository is mounted on VM host CSB303: /install/vmware_files 2011-10-07 15:02:07|624|607:607|image|VMware.pm:capture(596)|vmdk will be copied directly from VM host CSB303 to the image repository in the 2gbsparse disk format 2011-10-07 15:02:08|624|607:607|image|VMware.pm:get_vmhost_product_name(5405)|VMware product being used on VM host CSB303: 'VMware Server 1.0.10 build-203137' 2011-10-07 15:02:08|624|607:607|image|Linux.pm:file_exists(1404)|'/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk' exists on CSB303, files: 1, directories: 0, links: 0 2011-10-07 15:02:08|624|607:607|image|Linux.pm:file_exists(1404)|'/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk' exists on CSB303, files: 1, directories: 0, links: 0 |624|607:607|image| WARNING |624|607:607|image| 2011-10-07 15:02:08|624|607:607|image|VMware.pm:copy_vmdk(4781)|destination vmdk file path already exists on VM host CSB303: /install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk |624|607:607|image| ( 0) VMware.pm, copy_vmdk (line: 4781) |624|607:607|image| (-1) VMware.pm, capture (line: 600) |624|607:607|image| (-2) image.pm, process (line: 162) |624|607:607|image| (-3) vcld, make_new_child (line: 568) |624|607:607|image| (-4) vcld, main (line: 346) |624|607:607|image| WARNING |624|607:607|image| 2011-10-07 15:02:08|624|607:607|image|VMware.pm:capture(604)|failed to copy the vmdk files after the VM was powered off: '/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk' --> '/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk' |624|607:607|image| ( 0) VMware.pm, capture (line: 604) |624|607:607|image| (-1) image.pm, process (line: 162) |624|607:607|image| (-2) vcld, make_new_child (line: 568) |624|607:607|image| (-3) vcld, main (line: 346) 2011-10-07 15:02:08|624|607:607|image|Linux.pm:file_exists(1404)|'/install/vmware_files/vmwarelinux-MyCentOS357-v0/vmwarelinux-MyCentOS357-v0.vmdk' exists on CSB303, files: 1, directories: 0, links: 0 2011-10-07 15:02:09|624|60
