qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Frans de Boer <frans@fransdb.nl>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Problem with virtio
Date: Sun, 19 Sep 2010 23:13:16 +0200	[thread overview]
Message-ID: <4C967CEC.3060700@fransdb.nl> (raw)
In-Reply-To: <20100919155337.GA10730@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1902 bytes --]

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 <frans@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.

Frans.

[-- Attachment #2: Type: text/html, Size: 2572 bytes --]

  reply	other threads:[~2010-09-19 21:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 21:49 [Qemu-devel] Problem with virtio Frans de Boer
2010-09-16 23:40 ` Luiz Capitulino
2010-09-17  8:10   ` Frans de Boer
2010-09-18 21:13     ` Frans de Boer
2010-09-19 15:53       ` [Qemu-devel] " Michael S. Tsirkin
2010-09-19 21:13         ` Frans de Boer [this message]
2010-09-20 17:46           ` [Qemu-devel] " Michael S. Tsirkin
2010-09-20 20:22             ` [Qemu-devel] " Frans de Boer
2010-09-20 21:19               ` Vadim Rozenfeld
2010-09-20 23:15                 ` Frans de Boer
2010-09-25 23:06                   ` Frans de Boer
2010-09-26 15:30                   ` [Qemu-devel] " Michael S. Tsirkin
2010-09-26 18:02                     ` [Qemu-devel] " Frans de Boer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C967CEC.3060700@fransdb.nl \
    --to=frans@fransdb.nl \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).