From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=55156 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OxMMd-0004kM-1Z for qemu-devel@nongnu.org; Sun, 19 Sep 2010 12:03:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OxMIk-0007fk-Nw for qemu-devel@nongnu.org; Sun, 19 Sep 2010 11:59:39 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41946) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OxMIk-0007fZ-Fw for qemu-devel@nongnu.org; Sun, 19 Sep 2010 11:59:38 -0400 Date: Sun, 19 Sep 2010 17:53:37 +0200 From: "Michael S. Tsirkin" Message-ID: <20100919155337.GA10730@redhat.com> References: <4C9290FF.9050206@fransdb.nl> <20100916204042.51900cbe@doriath> <4C93225A.9040807@fransdb.nl> <4C952B68.7090601@fransdb.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C952B68.7090601@fransdb.nl> Subject: [Qemu-devel] Re: Problem with virtio List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Frans de Boer Cc: qemu-devel@nongnu.org On Sat, Sep 18, 2010 at 11:13:12PM +0200, Frans de Boer wrote: > On 09/17/2010 10:10 AM, Frans de Boer wrote: > > On 09/17/2010 01:40 AM, Luiz Capitulino wrote: > > > >> On Thu, 16 Sep 2010 23:49:51 +0200 > >> Frans de Boer wrote: > >> > >> > >> > >>> Dear reader, > >>> > >>> Using qemu-kvm-0.13-rc1 and having the boot partition as if=virtio, > >>> causes the attached blue screen when booting Windows XP SP3. > >>> Changing the interface to ide (if=ide) and the system boots normal. > >>> > >>> > >> Do you have the virtio drivers installed? > >> > >> > > Yes, everything is working fine when I use the 0.12.5 release. > > Before you ask, I am using the git repository too. Same effect. > > > > > No suggestions form anyone? > Again, any compile combination is working under 0.12.5. Starting with > 0.13-rc0/1 the virtio option for the boot disk is not working anymore. > > Frans. Could you try bisecting please? git bisect start v0.13.0-rc0 v0.12.0 will start the bisect process, then you build, test and run git bisect good/git bisect bad as appropriate to get the new version. -- MST