From: Paolo Bonzini <pbonzini@redhat.com>
To: Erik Rull <erik.rull@rdsoftware.de>
Cc: "Stefan Hajnoczi" <stefanha@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Benoît Canet" <benoit@irqsave.net>
Subject: Re: [Qemu-devel] Boot Problems Windows XP guest
Date: Wed, 28 Aug 2013 15:14:41 +0200 [thread overview]
Message-ID: <521DF7C1.50805@redhat.com> (raw)
In-Reply-To: <163348110.541056.1377680875692.open-xchange@email.1und1.de>
Il 28/08/2013 11:07, Erik Rull ha scritto:
>>> It could be a real difference, actually. An unexpectedly fast disk
>>> might screw a sloppy driver. IIRC you're not the first person reporting
>>> it. Stefan, do you think using block throttling could fix it (with some
>>> trial and error)?
>>
>> That might work. You could start with something like -drive ...,iops=20
>> and then disable the limit from the QEMU monitor once the guest OS is
>> booting (block_set_io_throttle virtio0 0 0 0 0 0 0).
>>
>> It would be easier to try -drive ...,cache=writethrough and -win2k-hack
>> first as Anthony suggests.
>>
>> Stefan
>
> Thanks.
> I tried that, but when should I reset the throttle?
Never. The bug will be there through the whole execution of the guest.
> When I reset it some seconds
> after the BIOS screen disappeared same result as without throttling. When I keep
> it, Windows still reboots, the cycle just takes longer (half an hour), but the
> progress seems to be the same as without throttle.
On second thought that is expected. Until throttling kicks in, I/O will
complete just as fast as without throttling. Maybe limiting the number
of bytes per second instead of I/O ops would be better. Can you try
-drive ...,bps=1048576 (possibly higher or lower numbers too)?
And maybe Benoit's new algorithm could help too. Benoit, do you have a
tree for Erik to try?
Paolo
next prev parent reply other threads:[~2013-08-28 13:15 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 [this message]
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
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=521DF7C1.50805@redhat.com \
--to=pbonzini@redhat.com \
--cc=benoit@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 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).