From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38381) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEfrC-0004Ed-2P for qemu-devel@nongnu.org; Wed, 28 Aug 2013 09:32:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VEfr4-0001yo-DJ for qemu-devel@nongnu.org; Wed, 28 Aug 2013 09:32:22 -0400 Received: from nodalink.pck.nerim.net ([62.212.105.220]:33693 helo=paradis.irqsave.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEfr4-0001yH-3D for qemu-devel@nongnu.org; Wed, 28 Aug 2013 09:32:14 -0400 Date: Wed, 28 Aug 2013 15:34:10 +0200 From: =?iso-8859-1?Q?Beno=EEt?= Canet Message-ID: <20130828133410.GB6170@irqsave.net> References: <586568842.455717.1377510746935.open-xchange@email.1und1.de> <20130827073833.GB24247@stefanha-thinkpad.redhat.com> <521D0B84.8040301@rdsoftware.de> <521D1AB0.1070904@redhat.com> <20130828075020.GA4696@stefanha-thinkpad.muc.redhat.com> <163348110.541056.1377680875692.open-xchange@email.1und1.de> <521DF7C1.50805@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <521DF7C1.50805@redhat.com> Content-Transfer-Encoding: quoted-printable 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" , Stefan Hajnoczi Le Wednesday 28 Aug 2013 =E0 15:14:41 (+0200), Paolo Bonzini a =E9crit : > 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 repo= rting > >>> 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 ...,iop= s=3D20 > >> and then disable the limit from the QEMU monitor once the guest OS i= s > >> booting (block_set_io_throttle virtio0 0 0 0 0 0 0). > >> > >> It would be easier to try -drive ...,cache=3Dwritethrough and -win2k= -hack > >> first as Anthony suggests. > >> > >> Stefan > >=20 > > Thanks. > > I tried that, but when should I reset the throttle? >=20 > Never. The bug will be there through the whole execution of the guest. >=20 > > 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. >=20 > On second thought that is expected. Until throttling kicks in, I/O wil= l > 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=3D1048576 (possibly higher or lower numbers too)? >=20 > And maybe Benoit's new algorithm could help too. Benoit, do you have a > tree for Erik to try? Hi Eric, You can find my latest throttling work on the leaky_continuous_final2 bra= nch of the following git tree. git clone git@gitorious.org:benoit-canet-qemu/benoit-canet-qemu.git git checkout leaky_continuous_final2 Hope this help Best regards Beno=EEt