Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1628847

Summary: [virtio-win][vioscsi+viostor] two jobs failed when run whql testing on win2008R2 system disk
Product: Red Hat Enterprise Linux 8 Reporter: lijin <lijin>
Component: virtio-winAssignee: Vadim Rozenfeld <vrozenfe>
Status: CLOSED NOTABUG QA Contact: lijin <lijin>
Severity: high Docs Contact:
Priority: high    
Version: 8.0CC: ailan, michen, mtessun, rbalakri, toneata, vrozenfe
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1691989 (view as bug list) Environment:
Last Closed: 2019-04-08 01:52:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1691989    
Attachments:
Description Flags
win2008R2 viostor hck package
none
win2008R2 vioscsi hck package
none
169-win2008R2-scsi-logs none

Description lijin 2018-09-14 07:45:13 UTC
Created attachment 1483220 [details]
win2008R2 viostor hck package

Description of problem:
2.2 TB Boot Test
Read Capacity 16 Unit Test - SCSI Compliance Test
Crashdump Support Test (LOGO)

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.12.0-12.el7.x86_64
kernel-3.10.0-938.el7.x86_64
seabios-bin-1.11.0-2.el7.noarch
virtio-win-1.9.6-1.el7.iso

How reproducible:
100%

Steps to Reproduce:
1.boot win2008R2 guest with blk/scsi disk:
/usr/libexec/qemu-kvm -name 160SCS2008R2TEC -enable-kvm -m 4G -smp 4 -uuid 5134b3e0-6078-411d-b3f9-2c8b1961bab0 -nodefconfig -nodefaults -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -chardev socket,id=charmonitor,path=/tmp/160SCS2008R2TEC,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -boot order=cd,menu=on -device piix3-usb-uhci,id=usb -drive file=160SCS2008R2TEC,serial=scsi-test,if=none,id=drive-ide0-0-0,format=raw,cache=none -device virtio-blk-pci,drive=drive-ide0-0-0,id=ide0-0-0,serial=scsi-test1 -drive file=/home/kvm_autotest_root/iso/ISO/Win2008R2/en_windows_server_2008_r2_standard_enterprise_datacenter_and_web_with_sp1_x64_dvd_617601.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=160SCS2008R2TEC.vfd,if=floppy,id=drive-fdc0-0-0,format=raw,cache=none -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=00:52:38:43:1b:b4 -device usb-tablet,id=input0 -vnc 0.0.0.0:10 -vga std -M pc

2. submit jobs in hck

Actual results:
following three jobs failed:
 - 2.2 TB Boot Test
 - Read Capacity 16 Unit Test - SCSI Compliance Test
 - Crashdump Support Test (LOGO)

Expected results:
job can pass

Additional info:
1. not regression bug as still reproduced with build 145;
2. As QE run scsi/blk whql testing on data disk, these three are not loaded during rhel7.6 certification;
3. Same jobs passed on win2012 guest

Comment 1 lijin 2018-09-14 07:45:57 UTC
Created attachment 1483221 [details]
win2008R2 vioscsi hck package

Comment 3 Vadim Rozenfeld 2019-03-15 00:03:51 UTC
Hi Li Jin,

Could you please try the latest build (b169) to see if these three problems are still reproducible?

Thank you,
Vadim.

Comment 5 lijin 2019-03-25 03:34:27 UTC
Still hit same errors with build169

Comment 6 Vadim Rozenfeld 2019-03-25 04:37:24 UTC
(In reply to lijin from comment #5)
> Still hit same errors with build169

Thanks.
Can you upload the most viostor and vioscsi recent HCK packages?

Best regards,
Vadim.

Comment 7 lijin 2019-03-25 05:33:54 UTC
Created attachment 1547594 [details]
169-win2008R2-scsi-logs

Comment 8 Vadim Rozenfeld 2019-03-26 08:38:45 UTC
(In reply to lijin from comment #7)
> Created attachment 1547594 [details]
> 169-win2008R2-scsi-logs

Thank you, Li Jin.

For the crash dump test problem could you please confirm the following things to me:
- the testing system connected to internet,
- system disk has at least 20G free space on partition C: ,
- paging file size is at least RAM size + 1MB big.

Comment 9 lijin 2019-03-27 02:59:08 UTC
(In reply to Vadim Rozenfeld from comment #8)
> (In reply to lijin from comment #7)
> > Created attachment 1547594 [details]
> > 169-win2008R2-scsi-logs
> 
> Thank you, Li Jin.
> 
> For the crash dump test problem could you please confirm the following
> things to me:
> - the testing system connected to internet,

  Yes, and I can see the symbols file in c:\symblos\

> - system disk has at least 20G free space on partition C: ,

  No, there are not 20G free space.
  Then I tried enlarge the disk, free space is more than 20G, but it still fail.

> - paging file size is at least RAM size + 1MB big.

   Yes, we set the paging file size larger than RAM.

Comment 10 Vadim Rozenfeld 2019-03-27 03:22:32 UTC
(In reply to lijin from comment #9)
> (In reply to Vadim Rozenfeld from comment #8)
> > (In reply to lijin from comment #7)
> > > Created attachment 1547594 [details]
> > > 169-win2008R2-scsi-logs
> > 
> > Thank you, Li Jin.
> > 
> > For the crash dump test problem could you please confirm the following
> > things to me:
> > - the testing system connected to internet,
> 
>   Yes, and I can see the symbols file in c:\symblos\
> 
> > - system disk has at least 20G free space on partition C: ,
> 
>   No, there are not 20G free space.
>   Then I tried enlarge the disk, free space is more than 20G, but it still
> fail.
> 
> > - paging file size is at least RAM size + 1MB big.
> 
>    Yes, we set the paging file size larger than RAM.

Thanks a lot.

There are two more things that can be related to this problem:
- Security Update for Windows 7 (KB2556532)  https://www.microsoft.com/en-us/download/details.aspx?id=27033
has to be installed,
- I also found a reference to filter 4704 which should resolve the problem if the hot-fix mentioned above was
not installed.

Comment 11 lijin 2019-03-27 06:48:18 UTC
(In reply to Vadim Rozenfeld from comment #10)

> There are two more things that can be related to this problem:
> - Security Update for Windows 7 (KB2556532) 
> https://www.microsoft.com/en-us/download/details.aspx?id=27033
> has to be installed,
> - I also found a reference to filter 4704 which should resolve the problem
> if the hot-fix mentioned above was
> not installed.

You're right, Vadim.
After I install the hotfix, "Crashdump Support Test (LOGO)" passed.

Now only two jobs failed:
2.2 TB Boot Test
Read Capacity 16 Unit Test - SCSI Compliance Test

Thank you very much

Comment 12 Vadim Rozenfeld 2019-04-04 07:13:50 UTC
(In reply to lijin from comment #11)
> (In reply to Vadim Rozenfeld from comment #10)
> 
> > There are two more things that can be related to this problem:
> > - Security Update for Windows 7 (KB2556532) 
> > https://www.microsoft.com/en-us/download/details.aspx?id=27033
> > has to be installed,
> > - I also found a reference to filter 4704 which should resolve the problem
> > if the hot-fix mentioned above was
> > not installed.
> 
> You're right, Vadim.
> After I install the hotfix, "Crashdump Support Test (LOGO)" passed.
> 
> Now only two jobs failed:
> 2.2 TB Boot Test
> Read Capacity 16 Unit Test - SCSI Compliance Test
> 
> Thank you very much

I managed to reproduce and then fix both issues. 
As we thought, the problem is not in the drivers themselves,
but in the testing environment. VM needs to be updated and WMF 4.0
(PowerShell 4.0) has to be installed.
(The simplest way to check PS version is to run $host.version command
from PS prompt).

Best regards,
Vadim.

Comment 13 lijin 2019-04-08 01:25:43 UTC
(In reply to Vadim Rozenfeld from comment #12)
> 
> I managed to reproduce and then fix both issues. 
> As we thought, the problem is not in the drivers themselves,
> but in the testing environment. VM needs to be updated and WMF 4.0
> (PowerShell 4.0) has to be installed.
> (The simplest way to check PS version is to run $host.version command
> from PS prompt).


After installing .NET Framework 4.5.1  and WDF4.0, these two jobs passed as well.

Thank you very much, Vadim.

Comment 14 Vadim Rozenfeld 2019-04-08 01:45:15 UTC
(In reply to lijin from comment #13)
> (In reply to Vadim Rozenfeld from comment #12)
> > 
> > I managed to reproduce and then fix both issues. 
> > As we thought, the problem is not in the drivers themselves,
> > but in the testing environment. VM needs to be updated and WMF 4.0
> > (PowerShell 4.0) has to be installed.
> > (The simplest way to check PS version is to run $host.version command
> > from PS prompt).
> 
> 
> After installing .NET Framework 4.5.1  and WDF4.0, these two jobs passed as
> well.
> 
> Thank you very much, Vadim.

Cool.
So, can we close it as notabug, since all three problems were VM
setup related?

Best regards,
Vadim.

Comment 15 lijin 2019-04-08 01:52:38 UTC
(In reply to Vadim Rozenfeld from comment #14)
> (In reply to lijin from comment #13)
> > (In reply to Vadim Rozenfeld from comment #12)
> > > 
> > > I managed to reproduce and then fix both issues. 
> > > As we thought, the problem is not in the drivers themselves,
> > > but in the testing environment. VM needs to be updated and WMF 4.0
> > > (PowerShell 4.0) has to be installed.
> > > (The simplest way to check PS version is to run $host.version command
> > > from PS prompt).
> > 
> > 
> > After installing .NET Framework 4.5.1  and WDF4.0, these two jobs passed as
> > well.
> > 
> > Thank you very much, Vadim.
> 
> Cool.
> So, can we close it as notabug, since all three problems were VM
> setup related?
> 
> Best regards,
> Vadim.

Sure.