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 <fr...@fransdb.nl> 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? > By the way, above ISO file contains much more virtio goodies not supplied yet > at the KVM or QEMU site. Maybe an upgrade at the site is in order? > > Frans. > >
