qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Bob Chen <a175818323@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	qemu block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] QEMU 1.1.2: block IO throttle might occasionally freeze running process's IO to zero
Date: Thu, 1 Dec 2016 11:16:28 +0100	[thread overview]
Message-ID: <e3da1cc4-f954-d4c1-bbda-cd3878c2aaab@redhat.com> (raw)
In-Reply-To: <CAMxP3BQptSjDJCoakSjT4CU-034rj4hgQ5JoQsoxMCk-3sQpKw@mail.gmail.com>



On 01/12/2016 05:07, Bob Chen wrote:
> Test case:
> 
> 1. QEMU 1.1.2
> 2. Run fio inside the vm, give it some pressure. Watch the realtime
> throughput
> 3. block_set_io_throttle drive_2 100000000 0 0 2000 0 0         #
> throttle bps and iops, any value
> 4. Observed that the IO is very likely to freeze to zero. The fio
> process stuck!
> 5. Kill the former fio process, start a new one. The IO turns back to normal
> 
> Didn't reproduce it with QEMU 2.5.
> 
> 
> Actually I'm not wishfully thinking the community would help fix this
> bug on such an ancient version. Just hope someone can tell me what is
> the root cause. Then I have to evaluate whether I should move to higher
> version QEMU, or fix this bug on 1.1.2 in-place(if it is a small one).

Hi,

throttling has been rewritten in QEMU 2.0 (see the commits around
5ddfffb, "throttle: Add a new throttling API implementing continuous
leaky bucket.", 2013-09-06), so the root cause is simply that the old
algorithms were buggy. :)

I think that the new implementation has been backported to QEMU versions
as old as 1.1.2, but if you can move to a newer version it would be simpler.

Paolo

      parent reply	other threads:[~2016-12-01 10:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01  4:07 [Qemu-devel] QEMU 1.1.2: block IO throttle might occasionally freeze running process's IO to zero Bob Chen
2016-12-01  9:52 ` Fam Zheng
2016-12-01 10:16 ` Paolo Bonzini [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e3da1cc4-f954-d4c1-bbda-cd3878c2aaab@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=a175818323@gmail.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).