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 1017009

Summary:	set_link command cause monitor show "virtio_ioport_write: unexpected address 0x13 value 0x0" with status=off
Product:	Red Hat Enterprise Linux 6	Reporter:	zhonglinzhang <zhzhang>
Component:	virtio-win	Assignee:	Yvugenfi <yvugenfi>
Status:	CLOSED WORKSFORME	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.5	CC:	acathrow, bcao, bsarathy, juzhang, michen, mkenneth, qzhang, virt-maint, xfu, zhzhang
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-02 05:41:42 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:

Description zhonglinzhang 2013-10-09 06:59:31 UTC

Description of problem:
Boot win2012 guest with "-device virtio-net-pci ... status=off", set_link virtio-net-pci0 off in qemu-kvm monitor, After a while in monitor show lots of "virtio_ioport_write: unexpected address 0x13 value 0x0" 

Version-Release number of selected component (if applicable):
host kernel: 2.6.32-421.el6.x86_64
qemu-kvm: qemu-kvm-0.12.1.2-2.410.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Boot a win2012 guest:
/usr/libexec/qemu-kvm -M pc -cpu SandyBridge -nodefaults -nodefconfig -enable-kvm -m 4G -smp 2,sockets=1,cores=2,threads=2 -name test \
-rtc base=localtime,clock=host,driftfix=slew  -k en-us  -boot menu=on  -vga qxl -vnc :1 -monitor stdio \
-drive file=/home/RHEL6.5-64.qcow2,if=none,id=drive-system-disk,media=disk,format=qcow2,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,scsi=on,bus=pci.0,drive=drive-system-disk,id=system-disk,bootindex=1,addr=0x5 \
-netdev tap,id=hostnet0,vhost=on,script=/etc/ovs-ifup,downscript=/etc/ovs-ifdown -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=00:22:15:27:54:8d,bus=pci.0,addr=0x9,status=off \
-usb -device usb-tablet

2. (qemu) set_link virtio-net-pci0 off

3. Inside guest:
# ping ......

Actual results:
In monitor show lots of information, link this:
(qemu) 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
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

Expected results:
Show no information in monitor

Additional info:
status=on/off  guest      set_link on/off      result
    on         win2012          on              normal
    on         win2012          off             normal
    off        win2012          on              normal
    off        win2012          off             warning information
    off         rhel6.5         off             normal

Comment 2 Mike Cao 2013-11-12 07:29:57 UTC

Pls retest this issue on virtio-win-1.6.7-2.el6

Comment 3 Yvugenfi@redhat.com 2013-12-01 10:04:10 UTC

1. Latest drivers should not have those printouts at all.

2. On other hand, please don't close this bug yet as it can point to other issues.

2.1. When you set link to off and see this message - can you disable the driver in the guest?
2.2. Is guest network alive after link set to on?


Thanks,
Yan.

Comment 4 zhonglinzhang 2013-12-02 05:30:39 UTC

Retest this with RHEL6.5 release version:
virtio-win-prewhql-0.1-74


Steps as Description:

After "(qemu) set_link virtio-net-pci0 off", But this time no show “virtio_ioport_write: unexpected address 0x13 value 0x0”



After "(qemu) set_link virtio-net-pci0 off", disable the driver in the guest, device Manager show "Not Responding", But close device Manager,once again display device Manager and will find the driver has already been disabled. 

From disable to enable can work well.
From enable to disable will show "Not Responding".