u'device': u'drive0', u'speed': 1, u'job_id': 122}]}
->block-job-cancel job_id=123
<- {u'return': {}}
--
Leiqzhang
Best Regards
> -Original Message-
> From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
> Sent: Th
On Thu, Apr 25, 2013 at 01:59:23AM +, Zhangleiqiang wrote:
> May be the "in_use" flag of "bs" at the "drive" unit is too large.
> Perhaps the "in_use" flag should just lock at the unit of one or some
> "image(s)" in the image chain, the "image(s)" needed to be locked are always
> the o
: Thursday, April 25, 2013 9:27 AM
> To: Stefan Hajnoczi
> Cc: Paolo Bonzini; qemu-devel@nongnu.org; Zhangleiqiang
> Subject: RE: [Qemu-devel] question about concurrent block job
>
> Hi, Stefan:
> Thanks for your relay.
>
> There are some jobs like drive-mirror, can keep
com]
> Sent: Wednesday, April 24, 2013 9:55 PM
> To: Zhangleiqiang
> Cc: Paolo Bonzini; qemu-devel@nongnu.org
> Subject: Re: [Qemu-devel] question about concurrent block job
>
> On Wed, Apr 24, 2013 at 12:28 PM, Zhangleiqiang
> wrote:
> > I found qemu does not
On Wed, Apr 24, 2013 at 12:28 PM, Zhangleiqiang
wrote:
> I found qemu does not support concurrently running multiple block
> jobs of the same drive (limited by the bs->in_use field). But there are
> indeed some type of block job can run concurrently, such as running block
> stream job
Hi, Paolo:
I found qemu does not support concurrently running multiple block jobs
of the same drive (limited by the bs->in_use field). But there are indeed some
type of block job can run concurrently, such as running block stream job while
running drive mirror, etc. Am I right ? Is it
