[pve-devel] [PATCH 2/2] remove migration lock from config.

Cesar Peschiera brain at click.com.py
Thu Sep 3 08:38:02 CEST 2015

I guess maintain the blockade of the VM also will be necessary when the disk
image is moved to other storage, also with the VM clone creation, and maybe
also for other functions that now i can't deduce.

But i don't know if the locking are developed for these functions .
(always thinking in the possibility of a task of backup scheduled to be
executed to the halfway through these other manual tasks).

----- Original Message ----- 
From: "Dietmar Maurer" <dietmar at proxmox.com>
To: "Wolfgang Link" <w.link at proxmox.com>; "Cesar Peschiera"
<brain at click.com.py>; <pve-devel at pve.proxmox.com>
Sent: Thursday, September 03, 2015 1:51 AM
Subject: Re: [pve-devel] [PATCH 2/2] remove migration lock from config.

>> And what will happen if i do a live migration, and halfway through, a
>> task
>> scheduled of backup is started?
> Yes, I guess we need to keep the lock (and find another solution for the
> problem).

More information about the pve-devel mailing list