On 01/30/2014 09:22 PM, Markus Stockhausen wrote:
> Von: users-bounces(a)ovirt.org [users-bounces(a)ovirt.org]"
im Auftrag von "Markus Stockhausen [stockhausen(a)collogia.de]
> Gesendet: Donnerstag, 30. Januar 2014 18:05
> An: ovirt-users
> Betreff: [Users] Migration failed (previous migrations succeded)
>
> Hello,
>
> we did some migration tests this day and all of a sudden the migration
> failed. That particular VM was moved around several times that day without
> any problems. During the migration the VM was running a download.
Found the reason. The memory was changing faster than the copy process
worked. The logs show:
Thread-289929::WARNING::2014-01-30 16:14:45,559::vm::800::vm.Vm::(run)
vmId=`ce64f528-9981-4ec6-a172-9d70a00a34cd`::Migration stalling: dataRemaining (19MiB)
> smallest_dataRemaining (9MiB). Refer to RHBZ#919201.
...
Thread-289929::WARNING::2014-01-30 16:14:55,561::vm::800::vm.Vm::(run)
vmId=`ce64f528-9981-4ec6-a172-9d70a00a34cd`::Migration stalling: dataRemaining (24MiB)
> smallest_dataRemaining (9MiB). Refer to RHBZ#919201.
...
Thread-289929::WARNING::2014-01-30 16:15:05,563::vm::800::vm.Vm::(run)
vmId=`ce64f528-9981-4ec6-a172-9d70a00a34cd`::Migration stalling: dataRemaining (20MiB)
> smallest_dataRemaining (9MiB). Refer to RHBZ#919201.
...
Now I' getting serious problems. During the migration the VM was
doing a rather slow download at 1,5 MB/s. So the memory changed
by 15 MB per 10 seconds. No wonder that a check every 10 seconds
was not able to see any progress. Im scared what will happen if I
want to migrate a medium loaded system runing a database.
Any tip for a parametrization?
Markus
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
what's the bandwidth? default is up to 30MB/sec, to allow up to 3 VMs to
migrate on 1Gb without congesting it.
you could raise that if you have 10GB, or raise the bandwidth cap and
reduce max number of concurrent VMs, etc.