<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:10pt"><div>Hello guys,</div><div>I'm having the following problem - I have two clusters which I want to use for migrating the VMs on, and one cluster is working as expected, but the other one is giving me headaches.</div><div>When I deploy a VM on Cluster #1 it switches to the RUNNING state very fast, but on Cluster #2 it stays in BOOT and won't continue booting correctly. Here is what the vm.log says:</div><div><br></div> <pre id="vm_log_id_6">Thu Sep 22 13:58:15 2011 [DiM][I]: New VM state is ACTIVE.<br>Thu Sep 22 13:58:15 2011 [LCM][I]: New VM state is PROLOG.<br>Thu Sep 22 13:58:15 2011 [VM][I]: Virtual Machine has no context<br>Thu Sep 22 13:58:23 2011 [TM][I]: tm_clone.sh: nebula1:/srv/cloud/one/one-templates/debian.qcow2 192.168.0.3:/srv/cloud/one/var//6/images/disk.0<br>Thu Sep 22 13:58:23 2011 [TM][I]: tm_clone.sh: DST:
/srv/cloud/one/var//6/images/disk.0<br>Thu Sep 22 13:58:23 2011 [TM][I]: tm_clone.sh: Creating directory /srv/cloud/one/var//6/images<br>Thu Sep 22 13:58:23 2011 [TM][I]: tm_clone.sh: Executed "mkdir -p /srv/cloud/one/var//6/images".<br>Thu Sep 22 13:58:23 2011 [TM][I]: tm_clone.sh: Executed "chmod a+w /srv/cloud/one/var//6/images".<br>Thu Sep 22 13:58:23 2011 [TM][I]: tm_clone.sh: Cloning /srv/cloud/one/one-templates/debian.qcow2<br>Thu Sep 22 13:58:23 2011 [TM][I]: tm_clone.sh: Executed "cp -r /srv/cloud/one/one-templates/debian.qcow2 /srv/cloud/one/var//6/images/disk.0".<br>Thu Sep 22 13:58:23 2011 [TM][I]: tm_clone.sh: Executed "chmod a+rw /srv/cloud/one/var//6/images/disk.0".<br>Thu Sep 22 13:58:23 2011 [LCM][I]: New VM state is BOOT<br>Thu Sep 22 13:58:23 2011 [VMM][I]: Generating deployment file: /srv/cloud/one/var/6/deployment.0<br><br>Everything seems to work, there are no permission issues etc. Also I'm having the same OS (Ubuntu Lucid Lynx),
the same libvirt and qemu version<br><br>Another thing I noticed - when I livemigrate a VM from cluster #1 to cluster #2 everything is as expected - "sudo virsh list" on the 2nd node also shows this VM as running.<br>However, when I now want to migrate this VM back from #2 to #1, the VM stays in MIGRATE state and doesn't continue<br><br>Any ideas???<br><br></pre></div></body></html>