<br>Hi,<br><br>after upgrading from vmware-2.98 to vmware-3.0.0 vm-templates that have more than one image no longer works, <br>because the first image is copied and then erased when the second is copied. <br><br>Here is a log:<br>
<br>Wed Dec  7 16:11:21 2011 [DiM][I]: New VM state is ACTIVE.<br>Wed Dec  7 16:11:21 2011 [LCM][I]: New VM state is PROLOG.<br>Wed Dec  7 16:11:21 2011 [VM][I]: Virtual Machine has no context<br>Wed Dec  7 16:13:05 2011 [TM][D]: tm_clone.sh: dev-clm1.init.se:/srv/cloud/one/var/images/6f741b4a8d3d1bce8898777ee74bfa49 dev-clmesx1.init.se:/srv/cloud/one/var//105/images/disk.0<br>
Wed Dec  7 16:13:05 2011 [TM][D]: tm_clone.sh: DST: /srv/cloud/one/var//105/images/disk.0<br>Wed Dec  7 16:13:05 2011 [TM][I]: tm_clone.sh: Creating directory /srv/cloud/one/var//105/images<br>Wed Dec  7 16:13:05 2011 [TM][I]: tm_clone.sh: Executed "rm -rf /srv/cloud/one/var//105/images".<br>
Wed Dec  7 16:13:05 2011 [TM][I]: tm_clone.sh: Executed "mkdir -p /srv/cloud/one/var//105/images/disk.0".<br>Wed Dec  7 16:13:05 2011 [TM][I]: tm_clone.sh: Executed "chmod a+w /srv/cloud/one/var//105/images/disk.0".<br>
Wed Dec  7 16:13:05 2011 [TM][I]: tm_clone.sh: Cloning /srv/cloud/one/var/images/6f741b4a8d3d1bce8898777ee74bfa49<br>Wed Dec  7 16:13:05 2011 [TM][I]: tm_clone.sh: Executed "cp -r /srv/cloud/one/var/images/6f741b4a8d3d1bce8898777ee74bfa49/* /srv/cloud/one/var//105/images/disk.0".<br>
Wed Dec  7 16:13:05 2011 [TM][I]: tm_clone.sh: Executed "chmod a+rw /srv/cloud/one/var//105/images/disk.0".<br>Wed Dec  7 16:13:05 2011 [TM][I]: ExitCode: 0<br>Wed Dec  7 16:13:07 2011 [TM][D]: tm_clone.sh: dev-clm1.init.se:/srv/cloud/one/var/images/a14fae29abc5f39fade2ebed13f61646 dev-clmesx1.init.se:/srv/cloud/one/var//105/images/disk.1<br>
Wed Dec  7 16:13:07 2011 [TM][D]: tm_clone.sh: DST: /srv/cloud/one/var//105/images/disk.1<br>Wed Dec  7 16:13:07 2011 [TM][I]: tm_clone.sh: Creating directory /srv/cloud/one/var//105/images<br>Wed Dec  7 16:13:07 2011 [TM][I]: tm_clone.sh: Executed "rm -rf /srv/cloud/one/var//105/images".<br>
Wed Dec  7 16:13:07 2011 [TM][I]: tm_clone.sh: Executed "mkdir -p /srv/cloud/one/var//105/images/disk.1".<br>Wed Dec  7 16:13:07 2011 [TM][I]: tm_clone.sh: Executed "chmod a+w /srv/cloud/one/var//105/images/disk.1".<br>
Wed Dec  7 16:13:07 2011 [TM][I]: tm_clone.sh: Cloning /srv/cloud/one/var/images/a14fae29abc5f39fade2ebed13f61646<br>Wed Dec  7 16:13:07 2011 [TM][I]: tm_clone.sh: Executed "cp -r /srv/cloud/one/var/images/a14fae29abc5f39fade2ebed13f61646/* /srv/cloud/one/var//105/images/disk.1".<br>
Wed Dec  7 16:13:07 2011 [TM][I]: tm_clone.sh: Executed "chmod a+rw /srv/cloud/one/var//105/images/disk.1".<br>Wed Dec  7 16:13:07 2011 [TM][I]: ExitCode: 0<br>Wed Dec  7 16:13:07 2011 [LCM][I]: New VM state is BOOT<br>
Wed Dec  7 16:13:07 2011 [VMM][I]: Generating deployment file: /srv/cloud/one/var/105/deployment.0<br>--- the boot gets stuck here because the OS-image no longer exist<br><br>The line that does "rm -rf /srv/cloud/one/var//105/images" was added in vmware-3.0.0<br>
<br>If I remove the rm line in /srv/cloud/one/lib/tm_commands/vmware/tm_clone.sh<br>starting the vm works.<br><br>I guess the proper way to solve this would be to do "rm -rf /srv/cloud/one/var//105/images/disk.<nr>" instead.<br>
<br>(I'm using opennebula-3.0.0)<br>
<br><br>mvh Håkan Isaksson<br><br>