qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: Paul Fisher <paul.fisher@elastichosts.com>
Cc: Yan Vugenfirer <yvugenfi@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Windows Virtio Issue
Date: Mon, 26 Mar 2012 17:51:37 +0200	[thread overview]
Message-ID: <201203261751.38264.vrozenfe@redhat.com> (raw)
In-Reply-To: <CAOkXnesBzJvRYHyONR2evC8E1VRPbuX6tw4ifhHxpFR8MdrUdg@mail.gmail.com>

On Monday, March 26, 2012 02:45:34 PM Paul Fisher wrote:
> On 26 March 2012 09:50, Vadim Rozenfeld <vrozenfe@redhat.com> wrote:
> > On Sunday, March 25, 2012 07:01:54 PM Yan Vugenfirer wrote:
> > Hi Paul,
> > Could you try reproducing this problem on "-smp 2" guest, with
> > small memory dump option turned on, instead of kernel memory dump.
> > 
> > Thanks,
> > Vadim.
> 
> Hi Vadim.
> 
> Thank you kindly for getting back to me.
> 
> I can certainly do that:
> 
> Dump and BSOD are in a zip at
> http://dl.dropbox.com/u/12332019/2200-VirtioBSOD-2.zip
> 
> This time running with 2 cores:
> 
> qemu-kvm -m 1024 -smp sockets=1,cores=2 -cpu host -nodefaults -vga cirrus
> -vnc :1  -drive if=none,id=block.0,format=raw,
> cache=writeback,file=drive.img -device
> virtio-blk-pci,bootindex=1,drive=block.0 -monitor stdio
> 
> Same procedure to get it to break - run crystal disk mark. Passed the
> stream read/write and 512k block read/write - broke at the seek intensive
> 4k level.
> 
> Regards,
> Paul

Hi Paul,
Managed to reproduce this problem, thank you. Going to fix it in the build.
Meanwhile, instead of writeback, could you  try cache=off ?

Best regards,
Vadim.

  reply	other threads:[~2012-03-26 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23 17:32 [Qemu-devel] Windows Virtio Issue Paul Fisher
2012-03-25 17:01 ` Yan Vugenfirer
2012-03-26  8:50   ` Vadim Rozenfeld
2012-03-26 12:45     ` Paul Fisher
2012-03-26 15:51       ` Vadim Rozenfeld [this message]
2012-04-04 10:18         ` emilien

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=201203261751.38264.vrozenfe@redhat.com \
    --to=vrozenfe@redhat.com \
    --cc=paul.fisher@elastichosts.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yvugenfi@redhat.com \
    /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).