Am 04/06/2018 um 01:24 PM schrieb Thomas Lamprecht:
Am 04/06/2018 um 12:28 PM schrieb Fabian Grünbichler:
On Fri, Apr 06, 2018 at 11:54:03AM +0200, Thomas Lamprecht wrote:
Move the locking inside worker, so that the process doing the actual
work (create or restore) holds the lock, and can call
Am 04/06/2018 um 12:28 PM schrieb Fabian Grünbichler:
On Fri, Apr 06, 2018 at 11:54:03AM +0200, Thomas Lamprecht wrote:
Move the locking inside worker, so that the process doing the actual
work (create or restore) holds the lock, and can call functions which
do locking without deadlocking.
On Fri, Apr 06, 2018 at 11:54:03AM +0200, Thomas Lamprecht wrote:
> Move the locking inside worker, so that the process doing the actual
> work (create or restore) holds the lock, and can call functions which
> do locking without deadlocking.
>
> This mirrors the behaviour we use for containers,
Move the locking inside worker, so that the process doing the actual
work (create or restore) holds the lock, and can call functions which
do locking without deadlocking.
This mirrors the behaviour we use for containers, and allows to add
an 'autostart' parameter which starts the VM after
