All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Erik Rull <erik.rull@rdsoftware.de>
Cc: "Benoît Canet" <benoit.canet@irqsave.net>,
	"Stefan Hajnoczi" <stefanha@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Boot Problems Windows XP guest
Date: Thu, 29 Aug 2013 16:55:35 +0200	[thread overview]
Message-ID: <521F60E7.80604@redhat.com> (raw)
In-Reply-To: <715136554.32957.1377787911389.open-xchange@email.1und1.de>

Il 29/08/2013 16:51, Erik Rull ha scritto:
> 
> 
>> On August 29, 2013 at 11:25 AM Benoît Canet <benoit.canet@irqsave.net> wrote:
>>
>>
>>> My commandline section is (I played with bps between 0.5 and 2.0 MB/sec and
>>> iops
>>> with 1000 and 500):
>>> -drive file=/dev/sda2,cache=none,bps=548576,bps_max=1,iops_max=1000
>>> Within qemu it looks like that:
>>> QEMU 1.6.50 monitor - type 'help' for more information
>>> (qemu) info block
>>> ide0-hd0: /dev/sda2 (raw)
>>>     I/O throttling:   bps=548576 bps_rd=0 bps_wr=0 bps_max=1 bps_rd_max=0
>>> bps_wr_max=0 iops=0 iops_rd=0 iops_wr=0 iops_max=1000 iops_rd_max=0
>>> iops_wr_max=0 iops_size=0
>>> (qemu)
>>
>> Why did you set iops_max but not iops ?
>>
>> Best regards
>>
>> Benoît
>>
> 
> Good point, I added that, but it still keeps rebooting:
> (qemu) info block
> ide0-hd0: /dev/sda2 (raw)
>     I/O throttling:   bps=548576 bps_rd=0 bps_wr=0 bps_max=1 bps_rd_max=0
> bps_wr_max=0 iops=500 iops_rd=0 iops_wr=0 iops_max=500 iops_rd_max=0
> iops_wr_max=0 iops_size=0

Too bad.

But iops_max w/o iops makes sense: it means no more than 1000 iops will
be in flight at the same time.  Note that "s" is a plural in "*s_max",
not "per seconds". :)

You could try iops_max=1 and make it higher if it works.

Paolo

  reply	other threads:[~2013-08-29 14:55 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
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 [this message]
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=521F60E7.80604@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=benoit.canet@irqsave.net \
    --cc=erik.rull@rdsoftware.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.