Re: [libvirt] [PATCHv4 02/18] blockjob: add API for async virDomainBlockJobAbort

2012-04-11 Thread Eric Blake
On 04/10/2012 03:30 PM, Eric Blake wrote: >> >> Okay, as I understand it, the only qemu binary that has a synchronous >> block_job_cancel command is the version that is part of RHEL6.2. So any >> compatibility code to allow for a synchronous block_job_cancel command >> in qemu would only ever make

Re: [libvirt] [PATCHv4 02/18] blockjob: add API for async virDomainBlockJobAbort

2012-04-10 Thread Eric Blake
On 04/10/2012 03:01 PM, Laine Stump wrote: > On 04/09/2012 11:52 PM, Eric Blake wrote: >> From: Adam Litke >> >> Qemu has changed the semantics of the "block_job_cancel" API. The original >> qed implementation (pretty much only backported to RHEL 6.2 qemu) was >> synchronous (ie. upon command com

Re: [libvirt] [PATCHv4 02/18] blockjob: add API for async virDomainBlockJobAbort

2012-04-10 Thread Laine Stump
On 04/09/2012 11:52 PM, Eric Blake wrote: > From: Adam Litke > > Qemu has changed the semantics of the "block_job_cancel" API. The original > qed implementation (pretty much only backported to RHEL 6.2 qemu) was > synchronous (ie. upon command completion, the operation was guaranteed to > be comp

[libvirt] [PATCHv4 02/18] blockjob: add API for async virDomainBlockJobAbort

2012-04-09 Thread Eric Blake
From: Adam Litke Qemu has changed the semantics of the "block_job_cancel" API. The original qed implementation (pretty much only backported to RHEL 6.2 qemu) was synchronous (ie. upon command completion, the operation was guaranteed to be completely stopped). With the new semantics going into q