Le 16/02/2010 16:05, Loiseleur Michel a écrit :
Live migration is an operation which can takes times, like 2 or 3 minutes for heavy
vms. Fixing this timeout work around another bug of db-o-matic: the infinite loop where
node A has a defined& stopped vm X and node B has a defined& running vm X. I
encountered this bug because the live migration has hit the timeout limit.
Signed-off-by: Loiseleur Michel<[email protected]>
---
src/task-omatic/taskomatic.rb | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/task-omatic/taskomatic.rb b/src/task-omatic/taskomatic.rb
index be244c9..c0a56b8 100755
--- a/src/task-omatic/taskomatic.rb
+++ b/src/task-omatic/taskomatic.rb
@@ -548,7 +548,7 @@ class TaskOmatic
dest_uri = "qemu+tcp://" + dest_node.hostname + "/system"
@logger.debug("Migrating from #{src_uri} to #{dest_uri}")
- result = vm.migrate(dest_uri, Libvirt::Domain::MIGRATE_LIVE, '', '', 0,
:timeout => 60 * 10)
+ result = vm.migrate(dest_uri, Libvirt::Domain::MIGRATE_LIVE, '', '', 0,
:timeout => 60 * 50)
@logger.error "Error migrating VM: #{result.text}" unless result.status
== 0
# undefine can fail, for instance, if we live migrated from A -> B, and
Applied on 'next' branch, since this pach is quite easy and I haven't
receive any comments on it.
Regards,
--
Loiseleur Michel
Directeur de l'OSSA
Linagora / 27, rue de Berri / 75008 PARIS
Tel/Fax : 01 58 18 68 41 / 01 58 18 68 29
http://www.08000linux.com/ | http://www.tosca-project.net
"Ce n'est pas le logiciel qui est libre, c'est vous"
_______________________________________________
Ovirt-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/ovirt-devel
