From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=49799 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OzvYy-0002KV-Qe for qemu-devel@nongnu.org; Sun, 26 Sep 2010 14:03:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OzvYx-0003ZF-BL for qemu-devel@nongnu.org; Sun, 26 Sep 2010 14:03:00 -0400 Received: from [83.160.137.85] (port=11182 helo=pubserv1.fransdb.nl) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OzvYx-0003Yv-1Z for qemu-devel@nongnu.org; Sun, 26 Sep 2010 14:02:59 -0400 Received: from localhost (localhost [127.0.0.1]) by pubserv1.fransdb.nl (Postfix) with ESMTP id 8676A4A4E for ; Sun, 26 Sep 2010 20:02:57 +0200 (CEST) Received: from pubserv1.fransdb.nl ([127.0.0.1]) by localhost (pubserv1.fransdb.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id IUJmmUTfHwIq for ; Sun, 26 Sep 2010 20:02:54 +0200 (CEST) Received: from [192.168.100.23] (unknown [192.168.100.23]) by pubserv1.fransdb.nl (Postfix) with ESMTPA id EBFA34465 for ; Sun, 26 Sep 2010 20:02:53 +0200 (CEST) Message-ID: <4C9F8ACD.6080905@fransdb.nl> Date: Sun, 26 Sep 2010 20:02:53 +0200 From: Frans de Boer MIME-Version: 1.0 References: <4C9290FF.9050206@fransdb.nl> <20100916204042.51900cbe@doriath> <4C93225A.9040807@fransdb.nl> <4C952B68.7090601@fransdb.nl> <20100919155337.GA10730@redhat.com> <4C967CEC.3060700@fransdb.nl> <20100920174641.GA30611@redhat.com> <4C97C292.3030104@fransdb.nl> <1285017553.1709.77.camel@localhost> <4C97EB0A.1010003@fransdb.nl> <20100926153019.GB21843@redhat.com> In-Reply-To: <20100926153019.GB21843@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: Problem with virtio List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: qemu-devel@nongnu.org On 09/26/2010 05:30 PM, Michael S. Tsirkin wrote: > On Tue, Sep 21, 2010 at 01:15:22AM +0200, Frans de Boer wrote: > >> On 09/20/2010 11:19 PM, Vadim Rozenfeld wrote: >> >>> On Mon, 2010-09-20 at 22:22 +0200, Frans de Boer wrote: >>> >>> >>>> On 09/20/2010 07:46 PM, Michael S. Tsirkin wrote: >>>> >>>> >>>>> On Sun, Sep 19, 2010 at 11:13:16PM +0200, Frans de Boer wrote: >>>>> >>>>> >>>>> >>>>>> On 09/19/2010 05:53 PM, Michael S. Tsirkin wrote: >>>>>> >>>>>> 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. >>>>>> >>>>>> >>>>>> >>>>>> Following your advice, I noticed that the system could not boot when I use the >>>>>> guest virtio driver. I then switch back to as far as version 10.0 with the >>>>>> same bad result. I then remembered that in the past I used the '.raw' format. >>>>>> Since I am using the qcow2 format (better performance), I never tried if=virtio >>>>>> for the disk before until I use the 0.13.0-rc1 version. I tried the release tar >>>>>> file of 0.12.5 and this time with the guest virtio driver, with the same bad >>>>>> result. >>>>>> Maybe it is the file format? Maybe the virtio disk driver? I have taken the >>>>>> virtio drivers from the KVM website. >>>>>> >>>>>> >>>>>> >>> Please try this one >>> http://people.redhat.com/vrozenfe/VioStorXp32.tar.gz >>> Cheers, >>> Vadim. >>> >>> >>>>>> Frans. >>>>>> >>>>>> >>>>>> >>>>> I got confused, sorry. Let's try to enumerate what works and what does not. >>>>> Could you tell us which of the following combinations you tried >>>>> and with what result (works/doesn't)? >>>>> >>>>> - virtio + raw + 0.12 >>>>> - virtio + qcow2 + 0.12 >>>>> - ide + qcow2 + 0.12 >>>>> >>>>> - virtio + raw + 0.13 >>>>> - virtio + qcow2 + 0.13 >>>>> - ide + qcow2 + 0.13 >>>>> >>>>> Thanks! >>>>> >>>>> >>>>> >>>>> >>>> I used 0.12.5 (git and tarball) and the 0.13-rc1 (git and tarball) >>>> >>>> - virtio + raw + 0.12 ok >>>> - virtio + qcow2 + 0.12 fail! >>>> - ide + qcow2 + 0.12 ok >>>> >>>> - virtio + raw + 0.13 fail! >>>> - virtio + qcow2 + 0.13 fail! >>>> - ide + qcow2 + 0.13 ok >>>> >>>> Frans. >>>> >>>> >> The new list is: >> >> - virtio + raw + 0.13 ok. >> >> That is when I am using this viostor driver: >> http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/ >> I used the complete ISO file and extracted the viostor files. These are 6.x files. >> >> .qcow2 with virtio still does not work under 0.13-rc1 >> It's late, so maybe in a few days I try 0.12.5 with the .qcow2 format. >> > OK, so with new drivers all formats behave identically > under 0.13 and 0.12, right? > > Yes, a image format in qcow2 is not working under versions 0.12-0.13 while using the latest - or previous - virtio drivers. The question is now if that is only in my case (and if so what "special" environment do I have) or are there others having the same issue. Which points to a design issue in either the qcow2 format or the virtio drivers.