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.
(In reply to Vadim Rozenfeld from comment #6)
> It will be very halpful to see setupapi.dev.log related to
> hckx file from https://bugzilla.redhat.com/attachment.cgi?id=801102
>
> Thanks,
> Vadim.
Hi Vadim
This time is strange,I didnot find the setupapi.dev.log file in the guest,only the setupapi.setup.log.
(In reply to lijin from comment #7)
> (In reply to Vadim Rozenfeld from comment #6)
> > It will be very halpful to see setupapi.dev.log related to
> > hckx file from https://bugzilla.redhat.com/attachment.cgi?id=801102
> >
> > Thanks,
> > Vadim.
>
> Hi Vadim
> This time is strange,I didnot find the setupapi.dev.log file in the
> guest,only the setupapi.setup.log.
Strange, it must be in the same directory as setupapi.setup.log - "c:\Windows\inf".
(In reply to Ronen Hod from comment #12)
> Mike,
> Where do we stand with this issue?
Sorry for forgot to update the status.
It is a guest image issue , following steps can workaround it
steps:
exec # Dism /Online /Cleanup-Image /RestoreHealth ,then reboot your SUT before the job start
lijin, pls mark it in somewhere
Mike
(In reply to Mike Cao from comment #13)
> (In reply to Ronen Hod from comment #12)
> > Mike,
> > Where do we stand with this issue?
>
> Sorry for forgot to update the status.
> It is a guest image issue , following steps can workaround it
>
> steps:
> exec # Dism /Online /Cleanup-Image /RestoreHealth ,then reboot your SUT
> before the job start
>
> lijin, pls mark it in somewhere
>
> Mike
Mark it in mojo document:https://mojo.redhat.com/docs/DOC-932910
Created attachment 801102 [details] win8-64-balloon-70 hck log Description of problem: job "Device Install Check for System File Consistency(certification)" always failed on win8-64 guest Version-Release number of selected component (if applicable): kernel-2.6.32-414.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.397.el6.x86_64 virtio-win-prewhql-0.1-70 spice-server-0.12.4-2.el6.x86_64 seabios-0.6.1.2-28.el6.x86_64 vgabios-0.6b-3.7.el6.noarch How reproducible: 100% Steps to Reproduce: 1.boot a win8-guest with following command: N_REPEAT=1 ; while true; do date; sleep 2; echo "test round: $N_REPEAT" ; N_REPEAT=$(($N_REPEAT+1)) && /usr/libexec/qemu-kvm \ -m 2G \ -smp 8,cores=8 \ -cpu cpu64-rhel6,+x2apic \ -usb \ -device usb-tablet \ -drive file=win8-64.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none \ -device ide-drive,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 \ -netdev tap,sndbuf=0,id=hostnet2,script=/etc/qemu-ifup,downscript=no \ -device e1000,netdev=hostnet2,mac=00:52:32:40:f2:10,bus=pci.0,addr=0x6 \ -uuid 7aa2ee19-60b3-4ab3-9e52-224c8e4f57e9 \ -rtc-td-hack \ -no-kvm-pit-reinjection \ -rtc base=localtime,clock=host,driftfix=slew \ -chardev socket,id=111a,path=/tmp/monitor-win8-64-balloon-70,server,nowait \ -mon chardev=111a,mode=readline \ -vnc :2 \ -vga cirrus \ -chardev socket,id=channel0,path=/tmp/tt,server,nowait \ -device virtio-balloon-pci,id=balloon0 \ -name win8-64-balloon-70-HCK \ -global PIIX4_PM.disable_s3=0 \ -global PIIX4_PM.disable_s4=0 \ -monitor stdio done 2.submit job in HCK Actual results: this job always failed Expected results: job can pass Additional info: attachment is the hck log file