similar to: [PATCH] Increase timeout for live migration

Displaying 20 results from an estimated 500 matches similar to: "[PATCH] Increase timeout for live migration"

2010 Aug 18
1
[PATCH] Setting the migration timeout to 3 minutes
--- 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 7de725d..0314e6a 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"
2010 Feb 25
1
[PATCH] fix storage problem.
Since Ruby::Qmf moves, the .key() method does not work anymore. It forces to use a .get_attr('key') in order to get the good value. Signed-off-by: Loiseleur Michel <mloiseleur at linagora.com> --- src/task-omatic/taskomatic.rb | 15 +++++++-------- 1 files changed, 7 insertions(+), 8 deletions(-) diff --git a/src/task-omatic/taskomatic.rb b/src/task-omatic/taskomatic.rb index
2009 Jun 25
0
[PATCH] Extend timeouts on libvirt calls.
This patch increases the timeout value on taskomatic calls so that we get back the real libvirt errors instead of just having qmf timeout. Signed-off-by: Ian Main <imain at redhat.com> --- src/task-omatic/task_storage.rb | 6 +++--- src/task-omatic/taskomatic.rb | 10 +++++----- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/src/task-omatic/task_storage.rb
2009 May 28
0
[PATCH server] Use qpid for migration and add more debugging to taskomatic.
This patch uses the qpid migration call which requires the latest libvirt-qpid and libvirt. I also add a bunch of debug logging here which is switchable but I've left it on for now so all users will have this in their logs. Signed-off-by: Ian Main <imain at redhat.com> --- src/task-omatic/taskomatic.rb | 36 ++++++++++++++++++++++++++++-------- 1 files changed, 28 insertions(+), 8
2010 Sep 30
1
libvirt-qpid and live migration
I have troubles with live migration since I upgraded libvirt on my nodes 1) I have to change 'Libvirt::Domain::MIGRATE_LIVE' to '1' in taskomatic error : Error: uninitialized constant Libvirt::Domain::MIGRATE_LIVE and why '1' : http://libvirt.org/html/libvirt-libvirt.html 2) the migration fails with this error : Task action processing failed: RuntimeError: Timed out
2009 Aug 26
2
Error starting a virtual machine
I've been playing with ovirt built from source. When I try to start my first VM, I get this error in taskomatic.log: INFO Wed Aug 26 14:33:28 -0600 2009 (12750) starting task_start_vm INFO Wed Aug 26 14:33:29 -0600 2009 (12750) VM will be started on node node94.ovirt.priv DEBUG Wed Aug 26 14:33:29 -0600 2009 (12750) Connecting volumes: DEBUG Wed Aug 26 14:33:29 -0600 2009 (12750) XML Domain
2009 May 29
1
[PATCH server] Don't set VM state to shut down in task.
This patch changes taskomatic so it only sets the VM to shutdown if the undefine succeeds. Otherwise it's possible a shutdown event could not succeed, or take a while as it often does, giving confusing messages to the user. Basically we're just letting dbomatic handle it now. Signed-off-by: Ian Main <imain at redhat.com> --- src/task-omatic/taskomatic.rb | 1 - 1 files
2009 May 29
1
[PATCH server] Also print reconnect message in log.
It seems people were getting confused by the message that taskomatic was disconnected and not logging a reconnect message. This patch makes it log on reconnect as well. Signed-off-by: Ian Main <imain at redhat.com> --- src/task-omatic/taskomatic.rb | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-) diff --git a/src/task-omatic/taskomatic.rb b/src/task-omatic/taskomatic.rb
2010 Sep 21
1
[PATCH] Check cpus capacity, not real cores.
Hi, is there a good reason why taskomatic check the number of real cores in the find_capable_host ? It prevents to use the full capacity of multithreading Signed-off-by: Arthur Clement <aclement at linagora.com> --- 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
2009 May 29
1
[PATCH server] Make taskomatic not do tasks if not connected to qpidd.
This patch just checks the broker to see if it's connected before attempting to implement tasks. Signed-off-by: Ian Main <imain at redhat.com> --- src/task-omatic/taskomatic.rb | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/src/task-omatic/taskomatic.rb b/src/task-omatic/taskomatic.rb index 5393c29..71432d2 100755 --- a/src/task-omatic/taskomatic.rb +++
2010 Sep 01
1
[PATCH 2/2] Adding the ability to select a Host to start a VM [2/2]
Signed-off-by: Simon Courtois <scourtois at linagora.com> --- src/task-omatic/taskomatic.rb | 5 ++--- 1 files changed, 2 insertions(+), 3 deletions(-) diff --git a/src/task-omatic/taskomatic.rb b/src/task-omatic/taskomatic.rb index 471ec88..1dfd74f 100755 --- a/src/task-omatic/taskomatic.rb +++ b/src/task-omatic/taskomatic.rb @@ -355,11 +355,10 @@ class TaskOmatic end end
2009 Sep 30
2
Few questions about oVirt install.
Hi. I have successfully installed ovirt. Boot 2 nodex throught PXE boot, and added to pool. Whe i try to create NFS storage, they in state: pending setup. How to add NFS storage? taskomatic.log INFO Wed Sep 30 16:59:09 +0300 2009 (1991) starting task_refresh_pool INFO Wed Sep 30 16:59:09 +0300 2009 (1991) storage_find_suitable_host: host node3.ovirt.priv uuid 30303234-3144-3832-4638-3931FF
2009 Jul 13
1
[PATCH] Use volume key instead of path to identify volume.
This patch teaches taskomatic to use the volume 'key' instead of the path from libvirt to key the volume off of in the database. This fixes the duplicate iscsi volume bug we were seeing. The issue was that libvirt changed the way they name storage volumes and included a local ID that changed each time it was attached. Note that the first run with this new patch will cause duplicate
2010 Sep 02
1
[PATCH 1/1] Introduce an option to always pxe-boot a vm.
Previously, a pxe-booted vm would always boot to HD at next startup. Signed-off-by: Nicolas Ochem <nicolas.ochem at alcatel-lucent.com> --- src/app/controllers/vm_controller.rb | 1 + src/app/models/vm.rb | 15 +++++++++++---- src/app/views/vm/_form.rhtml | 2 +- src/task-omatic/taskomatic.rb | 13 +++++++++++-- 4 files changed, 24 insertions(+), 7
2010 Aug 26
1
[PATCH] Adding the ability to select a Host to start a VM
Signed-off-by: Simon COURTOIS <scourtois at linagora.com> --- src/app/controllers/vm_controller.rb | 5 ++ src/app/models/vm_task.rb | 4 +- src/app/views/vm/start.rhtml | 77 ++++++++++++++++++++++++++++++++++ src/task-omatic/taskomatic.rb | 7 +++- 4 files changed, 91 insertions(+), 2 deletions(-) create mode 100644 src/app/views/vm/start.rhtml diff
2010 Aug 25
2
[PATCH] Virtio support
From: Simon Courtois <scourtois at linagora.com> Signed-off-by: Simon Courtois <scourtois at linagora.com> --- src/app/controllers/vm_controller.rb | 19 ++++++++++++++++- src/app/views/vm/_form.rhtml | 25 ++++++++++++++++++++--- src/db/migrate/044_add_virtio_to_vm_and_nic.rb | 11 ++++++++++ src/public/stylesheets/components.css | 5
2009 May 31
2
Storage problem latest build
I just build the latest ovirt from git and have a problem with storage now. Creating the storage pool works but when i try to add a volume i get "Pending_setup" and then in tasks "wrong number of arguments (1 for 2)". taskomatic log shows : ERROR Sun May 31 10:30:37 +0200 2009 (28807) Task action processing failed: ArgumentError: wrong number of arguments (1 for 2) ERROR Sun
2010 Sep 21
1
[PATCH] Introduce ability to select any kind of nic model, not just default or virtio.
There was no release since virtio support was introduced, so a proper migration is not necessary. Signed-off-by: Nicolas Ochem <nicolas.ochem at gmail.com> --- src/app/controllers/vm_controller.rb | 6 ++- src/app/models/nic.rb | 2 + src/app/views/vm/_form.rhtml | 25 +++++++++------- src/db/migrate/046_add_model_to_nic.rb | 29 ++++++++++++++++++
2009 Jul 07
1
[PATCH] Set up ovirt-agent so it starts as a daemon
This sets up ovirt-agent to start as a daemon along with dbomatic, taskomatic etc. While this is not ready for prime time I think it should be ok as you still require a valid, authenticated, connection to qpidd to access it. Signed-off-by: Ian Main <imain at redhat.com> --- installer/modules/ovirt/manifests/ovirt.pp | 6 +++ ovirt-server.spec.in | 5 ++
2010 Jun 08
1
[PATCH] Fix optimistic locking during vm migration
Signed-off-by: Loiseleur Michel <mloiseleur at linagora.com> --- src/db-omatic/db_omatic.rb | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/src/db-omatic/db_omatic.rb b/src/db-omatic/db_omatic.rb index da11bfa..79f29d2 100755 --- a/src/db-omatic/db_omatic.rb +++ b/src/db-omatic/db_omatic.rb @@ -195,6 +195,9 @@ class DbOmatic < Qmf::ConsoleHandler end