<div class="gmail_extra">Hi Carlos,</div><div class="gmail_extra"><br></div><div class="gmail_extra">can you send us some extra debugging info?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Create a new VM, exactly like you did with the previous email and launch it.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Supposing the VM has been deployed in dellblade01, send us the output of the following commands</div><div class="gmail_extra"><br></div><div class="gmail_extra">
# in dellblade01</div><div class="gmail_extra">$ ls -Rl /srv/cloud/one/<u></u>var//datastores/0/<VM_ID> </div><div class="gmail_extra"><br></div><div class="gmail_extra"># in the frontend</div><div class="gmail_extra">
$ bash -xv /srv/cloud/one/<u></u>var/remotes/tm/ssh/mv dellblade01:/srv/cloud/one/<u></u>var//datastores/0/<VM_ID>/disk.0 dellblade03:/srv/cloud/one/<u></u>var/datastores/0/<VM_ID>/disk.0</div><div class="gmail_extra">
<div class="gmail_extra">$ bash -xv /srv/cloud/one/<u></u>var/remotes/tm/ssh/mv dellblade01:/srv/cloud/one/<u></u>var//datastores/0/<VM_ID> dellblade03:/srv/cloud/one/<u></u>var//datastores/0/<VM_ID></div><div>
<br></div><div>Thanks!</div><div><br></div><div>Jaime</div><div><br></div><div class="gmail_quote">On Tue, Apr 24, 2012 at 5:36 PM, Carlos A. <span dir="ltr"><<a href="mailto:caralla@upv.es" target="_blank">caralla@upv.es</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I have also checked this option, but I found also a problem.<br>
<br>
If I change the system datastore (0) to set the TM_MAD ssh and then I create a new VM and try to migrate it, the vm.log fragment is next:<br>
<br>
------------------------------<u></u>------------------<br>
Tue Apr 24 17:17:07 2012 [LCM][I]: New VM state is SAVE_MIGRATE<br>
Tue Apr 24 17:17:10 2012 [VMM][I]: ExitCode: 0<br>
Tue Apr 24 17:17:10 2012 [VMM][I]: Successfully execute virtualization driver operation: save.<br>
Tue Apr 24 17:17:10 2012 [VMM][I]: ExitCode: 0<br>
Tue Apr 24 17:17:10 2012 [VMM][I]: Successfully execute network driver operation: clean.<br>
Tue Apr 24 17:17:11 2012 [LCM][I]: New VM state is PROLOG_MIGRATE<br>
Tue Apr 24 17:17:11 2012 [TM][I]: ExitCode: 0<br>
Tue Apr 24 17:17:15 2012 [TM][I]: mv: Moving dellblade01:/srv/cloud/one/<u></u>var//datastores/0/2985 to dellblade03:/srv/cloud/one/<u></u>var//datastores/0/2985<br>
Tue Apr 24 17:17:15 2012 [TM][I]: ExitCode: 0<br>
Tue Apr 24 17:17:15 2012 [LCM][I]: New VM state is BOOT<br>
Tue Apr 24 17:17:16 2012 [VMM][I]: ExitCode: 0<br>
Tue Apr 24 17:17:16 2012 [VMM][I]: Successfully execute network driver operation: pre.<br>
Tue Apr 24 17:17:16 2012 [VMM][I]: Command execution fail: /var/tmp/one/vmm/kvm/restore /srv/cloud/one/var//<u></u>datastores/0/2985/checkpoint dellblade03 2985 dellblade03<br>
Tue Apr 24 17:17:16 2012 [VMM][E]: restore: Command "virsh --connect qemu:///system restore /srv/cloud/one/var//<u></u>datastores/0/2985/checkpoint" failed: error: Failed to restore domain from /srv/cloud/one/var//<u></u>datastores/0/2985/checkpoint<br>
Tue Apr 24 17:17:16 2012 [VMM][I]: error: cannot close file: Bad file descriptor<br>
Tue Apr 24 17:17:16 2012 [VMM][E]: Could not restore from /srv/cloud/one/var//<u></u>datastores/0/2985/checkpoint<br>
Tue Apr 24 17:17:16 2012 [VMM][I]: ExitCode: 1<br>
Tue Apr 24 17:17:16 2012 [VMM][I]: Failed to execute virtualization driver operation: restore.<br>
Tue Apr 24 17:17:16 2012 [VMM][E]: Error restoring VM: Could not restore from /srv/cloud/one/var//<u></u>datastores/0/2985/checkpoint<br>
Tue Apr 24 17:17:16 2012 [DiM][I]: New VM state is FAILED<br>
------------------------------<u></u>------------------<br>
<br>
and the transfer.1.migrate file is<br>
<br>
------------------------------<u></u>------------------<br>
MV ssh dellblade01:/srv/cloud/one/<u></u>var//datastores/0/2985/disk.0 dellblade03:/srv/cloud/one/<u></u>var//datastores/0/2985/disk.0<br>
MV ssh dellblade01:/srv/cloud/one/<u></u>var//datastores/0/2985 dellblade03:/srv/cloud/one/<u></u>var//datastores/0/2985<br>
------------------------------<u></u>------------------<br>
<br>
Now I have the "checkpoint" file in dellblade03, but not the disk.0. This is strange because the transfer.1.migrate file tries to specifically move the disk.0 file but not the checkpoint file. I guess that the problem is the order of transferences in this case. I think that moving the folder once the disk has been moved is deleting the just moved disk. If I manually create a disk.0 file, I am able to manually restore the VM using virsh commands. Is there any way to solve this issue?<br>
<br>
On the other hand, I cannot see why the system datastore transfer mad needs to be set to ssh.<br>
<br>
Regards,<br>
Carlos A.<br>
<br>
El 24/04/12 17:17, Ruben S. Montero escribió:<div class="HOEnZb"><div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
Yes this may be the problem. Clould you check the output of<br>
onedatastore show 0 (and 1). The TM_MAD associated with the datastore<br>
should be ssh. If not, could you try to update it (onedatastore<br>
update). There should not be any "shared" keyword as you suggest.<br>
<br>
Note that the changes on the datastore (i.e. the actual TM used) are<br>
only reflected on new VMs. VMs created before the changes will use the<br>
original TM_MAD values...<br>
<br>
Cheers<br>
<br>
Ruben<br>
<br>
On Tue, Apr 24, 2012 at 5:07 PM, Carlos A.<<a href="mailto:caralla@upv.es" target="_blank">caralla@upv.es</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
I am upgrading my ONE 3.2 deployment to ONE 3.4 but I have one problem with<br>
migration of VM between nodes (not live migration).<br>
<br>
When using ONE 3.2 migration was fine, but now migration fails and I cannot<br>
find how to solve this problem.<br>
<br>
I have the default datastore, that it is a "filesystem" based on ssh tm_mad<br>
(and the system datastore "0").<br>
<br>
When I migrate the VM, I find the next vm.log fragment:<br>
------------------------------<u></u>------------------<br>
Tue Apr 24 16:53:51 2012 [LCM][I]: New VM state is SAVE_MIGRATE<br>
Tue Apr 24 16:53:54 2012 [VMM][I]: ExitCode: 0<br>
Tue Apr 24 16:53:54 2012 [VMM][I]: Successfully execute virtualization<br>
driver operation: save.<br>
Tue Apr 24 16:53:54 2012 [VMM][I]: ExitCode: 0<br>
Tue Apr 24 16:53:54 2012 [VMM][I]: Successfully execute network driver<br>
operation: clean.<br>
Tue Apr 24 16:53:54 2012 [LCM][I]: New VM state is PROLOG_MIGRATE<br>
Tue Apr 24 16:53:55 2012 [TM][I]: ExitCode: 0<br>
Tue Apr 24 16:53:55 2012 [TM][I]: ExitCode: 0<br>
Tue Apr 24 16:53:55 2012 [LCM][I]: New VM state is BOOT<br>
Tue Apr 24 16:53:55 2012 [VMM][I]: ExitCode: 0<br>
Tue Apr 24 16:53:55 2012 [VMM][I]: Successfully execute network driver<br>
operation: pre.<br>
Tue Apr 24 16:53:55 2012 [VMM][I]: Command execution fail:<br>
/var/tmp/one/vmm/kvm/restore<br>
/srv/cloud/one/var//<u></u>datastores/0/2984/checkpoint dellblade03 2984<br>
dellblade03<br>
------------------------------<u></u>------------------<br>
<br>
And the next transfer.1.migrate file appears<br>
------------------------------<u></u>------------------<br>
MV ssh dellblade01:/srv/cloud/one/<u></u>var//datastores/0/2984/disk.0<br>
dellblade03:/srv/cloud/one/<u></u>var//datastores/0/2984/disk.0<br>
MV shared dellblade01:/srv/cloud/one/<u></u>var//datastores/0/2984<br>
dellblade03:/srv/cloud/one/<u></u>var//datastores/0/2984<br>
------------------------------<u></u>------------------<br>
<br>
The problem is that the disk.0 file is not transfered to dellblade03. It<br>
seems that the phase of executing the transference of files is omited.<br>
<br>
Moreover the "shared" keyword appears while there is not any shared file<br>
system (but the system one that should not be considered when moving from<br>
one host to another). But also the checkpointing file is not moved.<br>
<br>
Note: migration from one host to the same host works (as expected). So virsh<br>
is able to restore the state of a saved VM.<br>
<br>
Any idea on this?<br>
<br>
Thank you in advance.<br>
<br>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/<u></u>listinfo.cgi/users-opennebula.<u></u>org</a><br>
</blockquote>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/<u></u>listinfo.cgi/users-opennebula.<u></u>org</a><br>
</div></div></blockquote></div><br></div><br clear="all"><div><br></div>-- <br>Jaime Melis<br>Project Engineer<br>OpenNebula - The Open Source Toolkit for Cloud Computing<br><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:jmelis@opennebula.org" target="_blank">jmelis@opennebula.org</a><br>