Re: [libvirt] [PATCH 4/4] qemu: Split handling of managed and unmanaged persistent reservations

2018-06-02 Thread Ján Tomko
On Thu, May 31, 2018 at 07:59:35PM +0200, Peter Krempa wrote: On Thu, May 31, 2018 at 19:30:25 +0200, Peter Krempa wrote: Add code that will handle the managed persistent reservations object separately from the unmanaged one. There is only one managed object so handling it with disks is awkward

Re: [libvirt] [PATCH 4/4] qemu: Split handling of managed and unmanaged persistent reservations

2018-05-31 Thread Peter Krempa
On Thu, May 31, 2018 at 19:30:25 +0200, Peter Krempa wrote: > Add code that will handle the managed persistent reservations object > separately from the unmanaged one. There is only one managed object so > handling it with disks is awkward and does not scale well when backing > chains come into vie

[libvirt] [PATCH 4/4] qemu: Split handling of managed and unmanaged persistent reservations

2018-05-31 Thread Peter Krempa
Add code that will handle the managed persistent reservations object separately from the unmanaged one. There is only one managed object so handling it with disks is awkward and does not scale well when backing chains come into view. Signed-off-by: Peter Krempa --- src/qemu/qemu_command.c