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.

Description of problem:
As mentioned in :https://bugzilla.redhat.com/show_bug.cgi?id=602607#c18,
create this bug to track the issue on virtio-win side.

This issue often happens when testing "NDIS Test6.0" or "NDIS test 6.5", guest hangs and cannot quit from qemu monitor. There's a lot of message like:

virtio_ioport_write: unexpected address 0x13 value 0x0
virtio_ioport_write: unexpected address 0x13 value 0x0
virtio_ioport_write: unexpected address 0x13 value 0x0
virtio_ioport_write: unexpected address 0x13 value 0x0
virtio_ioport_write: unexpected address 0x13 value 0x0
virtio_ioport_write: unexpected address 0x13 value 0x0
virtio_ioport_write: unexpected address 0x13 value 0x0



Version-Release number of selected component (if applicable):
virtio-win-1.1.7-2
qemu-kvm-0.12.1.2-2.90.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Boot a windows guest and test virtio-net driver, run jobs "NDIS Test6.0" or "NDIS test 6.5"
2.
3.
  
Actual results:
Guest hangs and got lots of "virtio_ioport_write" message.

Expected results:
Test pass.

Additional info:

Those printout are by design in virtio.

They are part of the debug mechanism in the guest driver that indicates loss (stuck) transfer on QEMU side. 

We will write 0 to VIRTIO_PCI_ISR in case of stuck transfer and "1" in case of blue screen.

The real issue here is the stuck transfer (packers submitted to QEMU but no indication received back).