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 1707192 - implement missing reset handler for cfi.pflash01 - slow train
Summary: implement missing reset handler for cfi.pflash01 - slow train
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: qemu-kvm
Version: 8.1
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.1
Assignee: Philippe Mathieu-Daudé
QA Contact: Xueqiang Wei
URL:
Whiteboard:
Depends On: 1678713
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-07 02:28 UTC by Xueqiang Wei
Modified: 2019-11-05 20:50 UTC (History)
16 users (show)

Fixed In Version: qemu-kvm-2.12.0-83.module+el8.1.0+3852+0ba8aef0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1678713
Environment:
Last Closed: 2019-11-05 20:49:21 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3345 0 None None None 2019-11-05 20:50:16 UTC

Comment 1 Xueqiang Wei 2019-05-07 02:31:09 UTC 
According to https://bugzilla.redhat.com/show_bug.cgi?id=1704584#c7, clone bug 1678713 to slow train.


Version-Release number of selected component (if applicable):

host: 
kernel-4.18.0-80.19.el8.x86_64
qemu-kvm-2.12.0-67.module+el8.1.0+3088+c3b61d6f
edk2-ovmf-20190308git89910a39dcfd-2.el8.noarch

guest: 
kernel-4.18.0-80.21.el8.x86_64
Comment 5 Xueqiang Wei 2019-08-07 06:01:27 UTC 
Hit this issue by automation case "system_reset_during_boot" in avocado, so retested with avocado.

Versions:
Host:
kernel-4.18.0-122.el8.x86_64
qemu-kvm-2.12.0-83.module+el8.1.0+3852+0ba8aef0
edk2-ovmf-20190308git89910a39dcfd-5.el8.noarch

Guest:
rhel8.1.0
windows2019
 

Both guest rhel8.1.0 and guest windows2019 are all work well after 40 times system_reset. So set status to VERIFIED.


cmd lines:
# python3 ConfigTest.py --testcase=system_reset_during_boot --imageformat=qcow2 --guestname=RHEL.8.1.0,Win2019 --driveformat=virtio_scsi --nicmodel=virtio_net --machines=q35 --clone=yes --firmware=ovmf


 (1/7) Host_RHEL.m8.u1.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.8.1.0.x86_64.io-github-autotest-qemu.unattended_install.cdrom.extra_cdrom_ks.default_install.aio_threads.q35: PASS (1832.82 s)
 (2/7) Host_RHEL.m8.u1.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.8.1.0.x86_64.io-github-autotest-qemu.rh_kernel_update.q35: PASS (424.67 s)
 (3/7) Host_RHEL.m8.u1.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2019.x86_64.io-github-autotest-qemu.unattended_install.cdrom.extra_cdrom_ks.default_install.aio_threads.q35: PASS (2030.70 s)

 (4/7) repeat1.Host_RHEL.m8.u1.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.8.1.0.x86_64.io-github-autotest-qemu.system_reset_during_boot.q35: PASS (661.35 s)
 (5/7) repeat1.Host_RHEL.m8.u1.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2019.x86_64.io-github-autotest-qemu.system_reset_during_boot.q35: PASS (1836.09 s)
 (6/7) repeat2.Host_RHEL.m8.u1.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.8.1.0.x86_64.io-github-autotest-qemu.system_reset_during_boot.q35: PASS (769.59 s)
 (7/7) repeat2.Host_RHEL.m8.u1.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2019.x86_64.io-github-autotest-qemu.system_reset_during_boot.q35: PASS (1172.72 s)

boot guest after system_reset:
 (1/2) Host_RHEL.m8.u1.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.8.1.0.x86_64.io-github-autotest-qemu.boot.q35: PASS (75.69 s)
 (2/2) Host_RHEL.m8.u1.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2019.x86_64.io-github-autotest-qemu.boot.q35: PASS (120.47 s)
Comment 7 errata-xmlrpc 2019-11-05 20:49:21 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3345
Note You need to log in before you can comment on or make changes to this bug.