Sorry, by overloaded I meant in terms of I/O, because this is an
active layer merge, the active layer
(aabf3788-8e47-4f8b-84ad-a7eb311659fa) is merged into the base image
(a78c7505-a949-43f3-b3d0-9d17bdb41af5), before the VM switches to use
it as the active layer. So if there is constantly additional data
written to the current active layer, vdsm may have trouble finishing
the synchronization

On Wed, May 27, 2020 at 4:55 PM David Sekne <> wrote:
> Hello,
> Yes, no problem. XML is attached (I ommited the hostname and IP).
> Server is quite big (8 CPU / 32 Gb RAM / 1 Tb disk) yet not overloaded. We 
> have multiple servers with the same specs with no issues.
> Regards,
> On Wed, May 27, 2020 at 2:28 PM Benny Zlotnik <> wrote:
>> Can you share the VM's xml?
>> Can be obtained with `virsh -r dumpxml <vm_name>`
>> Is the VM overloaded? I suspect it has trouble converging
>> taskcleaner only cleans up the database, I don't think it will help here
Users mailing list --
To unsubscribe send an email to
Privacy Statement:
oVirt Code of Conduct:
List Archives:

Reply via email to