On Mon, Apr 02, 2012 at 09:49:38 -0600, Eric Blake wrote:
> On 04/02/2012 08:20 AM, Jiri Denemark wrote:
> > Originally, qemuDomainCheckEjectableMedia was entering monitor with qemu
> > driver lock. Commit 2067e31bf97667eab9f111b496f5e9a44e827c5b, which I
> > made to fix that, revealed another issu
On 04/02/2012 08:20 AM, Jiri Denemark wrote:
> Originally, qemuDomainCheckEjectableMedia was entering monitor with qemu
> driver lock. Commit 2067e31bf97667eab9f111b496f5e9a44e827c5b, which I
> made to fix that, revealed another issue we had (but didn't notice it
> since the driver was locked): we
Originally, qemuDomainCheckEjectableMedia was entering monitor with qemu
driver lock. Commit 2067e31bf97667eab9f111b496f5e9a44e827c5b, which I
made to fix that, revealed another issue we had (but didn't notice it
since the driver was locked): we didn't set nested job when
qemuDomainCheckEjectableMe