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 10:50:26 +0200	[thread overview]
Message-ID: <201203261050.27200.vrozenfe@redhat.com> (raw)
In-Reply-To: <EC12DF16-D4CE-4A6D-A9BE-60D71C98BDD3@redhat.com>

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.

> Hello Paul,
> 
> Vadim is the owner of virtio-block Windows driver. He will try to help you.
> 
> Best regards,
> Yan.
> 
> On Mar 23, 2012, at 7:32 PM, Paul Fisher wrote:
> > Dear Yan,
> > 
> > We seem to be having some trouble with virtio disk on Windows Server 2008
> > R2 running on qemu-kvm. Essentially, when disk IO is stressed, it seems
> > to blue screen.
> > 
> > 
> > These are potentially contended disks, since it's public cloud with
> > multiple customers on the host - the issue could be connected to
> > contention making disk response slow?
> > 
> > Pertinent facts:
> > 
> > * qemu-kvm 1.0
> > 
> > * Hosts have linux kernel 3.2.2, 64 bit, AMD Opteron 6128
> > 
> > * VM is Windows Server 2008 R2, 64 bit - all patches downloaded from MS
> > 
> > * Virtio disk drivers are the February 2012 release .2200. Problem is
> > apparent with the older .2000 driver as well.
> > 
> > * Blue screen shows failure in viostor.sys - screen cap and minidump are
> > at http://dl.dropbox.com/u/12332019/2200BSOD.zip
> > 
> > 
> > * Replication: Yes. Easily. In this case I stressed the disk by running
> > Crystal Disk mark (a free IO measuring tool). When it got to the 4 KB
> > random seek tests - I think it was on write - it would consistently blue
> > screen.
> > 
> > * If it would help, I can provide remote access to this virtual machine
> > if you wish - it's in our cloud system.
> > 
> > * qemu-kvm command line:
> > 
> > 
> > 
> > qemu-kvm -m MEMORY -smp SMP -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
> > 
> > Any help would be greatly appreciated.
> > 
> > Regards,
> > Paul Fisher
> > Operations Manager
> > ElasticHosts Ltd

  reply	other threads:[~2012-03-26  8:50 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 [this message]
2012-03-26 12:45     ` Paul Fisher
2012-03-26 15:51       ` Vadim Rozenfeld
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=201203261050.27200.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).