* [Qemu-devel] Windows Virtio Issue
@ 2012-03-23 17:32 Paul Fisher
2012-03-25 17:01 ` Yan Vugenfirer
0 siblings, 1 reply; 6+ messages in thread
From: Paul Fisher @ 2012-03-23 17:32 UTC (permalink / raw)
To: Yan Vugenfirer; +Cc: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1752 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] Windows Virtio Issue
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
0 siblings, 1 reply; 6+ messages in thread
From: Yan Vugenfirer @ 2012-03-25 17:01 UTC (permalink / raw)
To: Paul Fisher, Vadim Rozenfeld; +Cc: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 2192 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] Windows Virtio Issue
2012-03-25 17:01 ` Yan Vugenfirer
@ 2012-03-26 8:50 ` Vadim Rozenfeld
2012-03-26 12:45 ` Paul Fisher
0 siblings, 1 reply; 6+ messages in thread
From: Vadim Rozenfeld @ 2012-03-26 8:50 UTC (permalink / raw)
To: Paul Fisher; +Cc: Yan Vugenfirer, qemu-devel
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] Windows Virtio Issue
2012-03-26 8:50 ` Vadim Rozenfeld
@ 2012-03-26 12:45 ` Paul Fisher
2012-03-26 15:51 ` Vadim Rozenfeld
0 siblings, 1 reply; 6+ messages in thread
From: Paul Fisher @ 2012-03-26 12:45 UTC (permalink / raw)
To: Vadim Rozenfeld; +Cc: Yan Vugenfirer, qemu-devel
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1339 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Qemu-devel] Windows Virtio Issue
2012-03-26 12:45 ` Paul Fisher
@ 2012-03-26 15:51 ` Vadim Rozenfeld
2012-04-04 10:18 ` emilien
0 siblings, 1 reply; 6+ messages in thread
From: Vadim Rozenfeld @ 2012-03-26 15:51 UTC (permalink / raw)
To: Paul Fisher; +Cc: Yan Vugenfirer, qemu-devel
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-04-04 10:46 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2012-04-04 10:18 ` emilien
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).