qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Erik Rull <erik.rull@rdsoftware.de>
Subject: Re: [Qemu-devel] Boot Problems Windows XP guest
Date: Wed, 28 Aug 2013 13:05:26 +0200	[thread overview]
Message-ID: <521DD976.1000608@redhat.com> (raw)
In-Reply-To: <CA+aC4ksSdbY3mzosXR7Z9Do1JrfY+mdkt9d99oqBqOi3Dk67_g@mail.gmail.com>

Il 27/08/2013 23:37, Anthony Liguori ha scritto:
> On Aug 27, 2013 4:32 PM, "Paolo Bonzini" <pbonzini@redhat.com
> <mailto:pbonzini@redhat.com>> wrote:
>>
>> Il 27/08/2013 22:26, Erik Rull ha scritto:
>> > Hi Stefan,
>> >
>> > which BIOS is selected by default?
>>
>> QEMU only ships with SeaBIOS.
>>
>> > It's more a guess, there must be a
>> > change between 1.2.0 and 1.6.0 that prevents a simple Windows XP from
>> > booting completely, if the guest HDD image is placed on a SSD. On a
>> > rotating HDD (with the same commandline except the path to the image) it
>> > boots successfully. The only difference is the speed of the disk access.
>>
>> 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)?
> 
> Add cache=writethrough and I bet it'll work even on an SSD.

You'll also kill the SSD rather quickly though. :)

Paolo

> We changed the default in that timeframe.  The Windows IDE drivers can
> have an issue if the IRQ comes too quickly to indicate the request has
> completed.  This is what -win2k-hack is for.  That may also work here too.

  parent reply	other threads:[~2013-08-28 11:06 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 [this message]
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
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=521DD976.1000608@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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).