Bug 752045

Summary: KVM :Blue screen-'win7 32 bit iscsi storage domain' when trying to load driver for virtio disk.
Product: Red Hat Enterprise Linux 6 Reporter: Tomer <tbenshos>
Component: virtio-winAssignee: Vadim Rozenfeld <vrozenfe>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2CC: acathrow, bcao, bsarathy, ehabkost, juzhang, mkenneth, tburke, virt-maint, yvugenfi
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-08 20:52:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Screenshot blue screen none

Description Tomer 2011-11-08 12:15:55 UTC
Description of problem:

Blue screen when trying to install windows7 32 bit with virtio disk.
happen with iscsi storage domain only!
installing Windows7 32 bit with vfd floppy disk that contain viostor driver for virtio
disk. 
Blue screen happen right after viostor.inf loaded in order to prepare the
virtio disk to be bootable disk for windows installation.

virtio version 1.4.0
ic147
vdsm-4.9-110.el6.x86_64
qemu-kvm-0.12.1.2-2.192.el6.x86_64

Comment 2 Eduardo Habkost 2011-11-08 12:52:18 UTC
Moving to virtio-win, as it looks like an issue with the driver.

Comment 3 Yvugenfi@redhat.com 2011-11-08 20:37:13 UTC
Do you have dump file from the guest?

Comment 4 Tomer 2011-11-09 09:07:26 UTC
No, I don't have dump file because it happened during installation

Comment 5 Vadim Rozenfeld 2011-11-09 09:31:27 UTC
(In reply to comment #4)
> No, I don't have dump file because it happened during installation

Can you capture BSOD screen? 
Or, at least, the Bug Check code number?

Best,
Vadim.

Comment 6 Tomer 2011-11-09 09:43:19 UTC
Created attachment 532510 [details]
Screenshot blue screen

Comment 7 Tomer 2011-11-09 09:48:41 UTC
I'm sure I've done this before, I do not know how it disappeared.
I've attached it again. :)

Comment 8 Dor Laor 2011-11-09 10:09:21 UTC
Does ide works for win7 over this iscsi setup?

Comment 9 Vadim Rozenfeld 2011-11-09 13:08:43 UTC
Not that it provides some sort of useful information, 
but thanks anyway :)

You said it happens on iscsi only, right?
Is there any way to measure IO latency over iscsi?

Best,
Vadim.

Comment 11 Tomer 2011-11-16 09:42:03 UTC
I don't know if is the same problem, but this reproduced with guest_tools 3.0.26 and 3.0.29.

now it's happen with nfs, with IDE hard disk, COW format.
Blue screen appear for a sec during rebooting after tools installation finished.
and the vm rebooting again in looping.

Comment 12 Vadim Rozenfeld 2011-11-16 12:09:15 UTC
(In reply to comment #11)
> I don't know if is the same problem, but this reproduced with guest_tools
> 3.0.26 and 3.0.29.
> 
> now it's happen with nfs, with IDE hard disk, COW format.

Can you try reproducing the problem with a local storage?
Cheers,
Vadim.

> Blue screen appear for a sec during rebooting after tools installation
> finished.
> and the vm rebooting again in looping.

Comment 13 Mike Cao 2011-11-22 08:16:25 UTC
(In reply to comment #11)
> I don't know if is the same problem, but this reproduced with guest_tools
> 3.0.26 and 3.0.29.
> 
> now it's happen with nfs, with IDE hard disk, COW format.

Hi ,Vadim

Does this mean this is not a virtio-win issue ,should be a issue in storage configuration ?
BTW,we do accptance test for each virtio-win build in local hard disk ,did not hit this issue.

Best Regards,
Mike

Comment 14 Vadim Rozenfeld 2011-11-22 09:00:05 UTC
(In reply to comment #13)
> (In reply to comment #11)
> > I don't know if is the same problem, but this reproduced with guest_tools
> > 3.0.26 and 3.0.29.
> > 
> > now it's happen with nfs, with IDE hard disk, COW format.
> 
> Hi ,Vadim
> 
> Does this mean this is not a virtio-win issue ,should be a issue in storage
> configuration ?
Yes, I'm almost sure that it is a storage problem. Let's see if Tomer can reproduce it on a local storage.

Cheers,
Vadim.

> BTW,we do accptance test for each virtio-win build in local hard disk ,did not
> hit this issue.
> 
> Best Regards,
> Mike

Comment 15 Vadim Rozenfeld 2011-12-08 20:52:42 UTC
Closing the bug, because it is not a Windows driver issue, but rather a
storage configuration problem.

Comment 18 Tomer 2012-01-10 09:49:52 UTC
Is not reproduced with local storage.