qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Benoît Canet" <benoit.canet@irqsave.net>
To: Erik Rull <erik.rull@rdsoftware.de>
Cc: "Benoît Canet" <benoit.canet@irqsave.net>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Stefan Hajnoczi" <stefanha@gmail.com>
Subject: Re: [Qemu-devel] Boot Problems Windows XP guest
Date: Wed, 28 Aug 2013 20:40:42 +0200	[thread overview]
Message-ID: <20130828184042.GG6170@irqsave.net> (raw)
In-Reply-To: <521E3F9E.8010808@rdsoftware.de>

> thanks for your help. I cloned the git and compiled it - but I'm not
> completely sure how to enable the throttling finally - there were
> several mails regarding averages and max values... And the "unit" of
> the values would be interesting.

Hi Erik,

The main settings are bps, bps_rd and bps_wr for total, read and write bandwith
throttling (unit is bytes) and iops, iops_rd, iops_wr for IO per second
throttling (unit is IO operation).

You should specify your settings on the -drive command line like in:
-drive file=foo.raw,if=virtio,cache=none,bps=1048576 for a 1 MB total bandwith.

In addition to that there is another set of parameters to configure the burst
ability of the throttling.
These setting are: bps_max, bps_rd_max, bps_wr_max, iops_mx, iops_rd_max, and
iops_wr_max.

Some bursting is enabled by default.

>From what Paolo said you should set bps_max = 1 to specify that the default
bursting is not set.

So:
-drive file=foo.raw,if=virtio,cache=none,bps=1048576,bps_max=1 for a 1 MB total
bandwith with almost no burst.

Best regards

Benoît

ps: take care of updating your repository and recompiling it since I made some
changes for you to use. (use git fetch origin)

> 
> Merci beaucoup.
> 
> Best regards,
> 
> Erik
> 
> 
> 

  reply	other threads:[~2013-08-28 18:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26  9:52 [Qemu-devel] Boot Problems Windows XP guest Erik Rull
2013-08-27  7:38 ` Stefan Hajnoczi
2013-08-27 20:26   ` Erik Rull
2013-08-27 21:31     ` Paolo Bonzini
2013-08-27 21:37       ` Anthony Liguori
2013-08-28  8:05         ` Erik Rull
2013-08-28 11:05         ` Paolo Bonzini
2013-08-28  7:50       ` Stefan Hajnoczi
2013-08-28  9:07         ` Erik Rull
2013-08-28 13:14           ` Paolo Bonzini
2013-08-28 13:34             ` Benoît Canet
2013-08-28 13:41               ` Paolo Bonzini
2013-08-28 13:51                 ` Benoît Canet
2013-08-28 13:59                   ` Paolo Bonzini
2013-08-28 14:05                     ` Benoît Canet
2013-08-28 14:05                       ` Paolo Bonzini
2013-08-28 14:26                         ` Benoît Canet
2013-08-28 18:21                           ` Erik Rull
2013-08-28 18:40                             ` Benoît Canet [this message]
2013-08-28 19:22                               ` Erik Rull
2013-08-29  7:53                                 ` Erik Rull
2013-08-29  9:25                                   ` Benoît Canet
2013-08-29 14:51                                     ` Erik Rull
2013-08-29 14:55                                       ` Paolo Bonzini
2013-08-29 15:31                                         ` Erik Rull
2013-08-28 13:19           ` Stefan Hajnoczi

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=20130828184042.GG6170@irqsave.net \
    --to=benoit.canet@irqsave.net \
    --cc=erik.rull@rdsoftware.de \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).