From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53004) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEaWh-0001mK-PP for qemu-devel@nongnu.org; Wed, 28 Aug 2013 03:51:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VEaWZ-0006ey-IT for qemu-devel@nongnu.org; Wed, 28 Aug 2013 03:50:51 -0400 Received: from mail-ea0-f169.google.com ([209.85.215.169]:54505) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEaWZ-0006es-Bo for qemu-devel@nongnu.org; Wed, 28 Aug 2013 03:50:43 -0400 Received: by mail-ea0-f169.google.com with SMTP id k11so2777478eaj.28 for ; Wed, 28 Aug 2013 00:50:27 -0700 (PDT) Date: Wed, 28 Aug 2013 09:50:20 +0200 From: Stefan Hajnoczi Message-ID: <20130828075020.GA4696@stefanha-thinkpad.muc.redhat.com> References: <586568842.455717.1377510746935.open-xchange@email.1und1.de> <20130827073833.GB24247@stefanha-thinkpad.redhat.com> <521D0B84.8040301@rdsoftware.de> <521D1AB0.1070904@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <521D1AB0.1070904@redhat.com> Subject: Re: [Qemu-devel] Boot Problems Windows XP guest List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Erik Rull , "qemu-devel@nongnu.org" On Tue, Aug 27, 2013 at 11:31:28PM +0200, Paolo Bonzini wrote: > Il 27/08/2013 22:26, Erik Rull ha scritto: > > 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)? 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