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 1270149

Summary:	[virtio-win][netkvm] Check guest network link status of virtio nic with status=on failed (build 110)
Product:	Red Hat Enterprise Linux 7	Reporter:	Yu Wang <wyu>
Component:	virtio-win	Assignee:	Yvugenfi <yvugenfi>
virtio-win sub component:	virtio-win-prewhql	QA Contact:	Virtualization Bugs <virt-bugs>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	lijin, lmiksik, vrozenfe
Version:	7.2
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	NO_DOCS	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-04 08:49:18 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 Yu Wang 2015-10-09 06:19:40 UTC

Check guest network link status of virtio nic with status=on failed (build 110)

Steps to Reproduce:
1 boot up guest with following cli (status=on)

/usr/libexec/qemu-kvm -name win7-32 -enable-kvm -m 2G -smp 4 -uuid ae361e8d-28a4-4e70-8783-bda0d450ce35 -nodefconfig --nodefaults -chardev socket,id=charmonitor,path=/tmp/win7-32,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -boot order=cd,menu=on -drive file=win.raw,if=none,id=drive-ide0-0-0,format=raw,serial=mike_cao,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=driver.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 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=isa_serial0 -vga qxl -spice disable-ticketing,port=5909 -monitor stdio -qmp tcp:0:4446,server,nowait -netdev tap,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown,id=hostnet1,vhost=off,queues=4, -device virtio-net-pci,netdev=hostnet1,id=net1,mac=1a:46:0b:ca:bc:8c,bus=pci.0,mq=on,vectors=10,status=on

2.Inside guest, ping out from guest

3.Under qemu monitor, set network link down.
(qemu)set_link net1 off

4.Inside guest, ping out from guest

5.Reboot guest inside
# ctrl+alt+del --> reboot

6.Inside guest, ping out from guest

7.Reboot guest via qemu monitor
(qemu) system_reset

8.Inside guest, ping out from guest

9.Under qemu monitor, set network link up.
(qemu)set_link net1 on

10.Inside guest, ping out from guest


Actual results:

After step 3,the network status is still on, can not ping out
After step 9,the network status is still off and can not ping out

Expected results:
After step 3, the network status is off, can not ping out
After step 9,the network status is on and can ping out


Additional info:

1 All the windows guests hit this issue.
2 build 105 and 7.1.z don't hit this issue, so it is a regression bug.
3 Workaround:
  After step 9, disable/enable this driver on device manager, the network can ping out.
  After step 9, reboot the guest, the network status is on and can ping out.

Comment 2 Yu Wang 2015-12-08 00:26:47 UTC

Reproduced this issue on virtio-win-prewhql-110 version
Verified this issue on virtio-win-prewhql-111 version

Steps same as comment#0

Actual Results:
on virtio-win-prewhql-110 (un-fixed version) version, this issue can be reproduced
on virtio-win-prewhql-111 (fix version), the network status is normally, and can/cannot ping out, no more reproduced

Base on above, this issue has been fixed already.

Comment 3 lijin 2015-12-08 01:57:51 UTC

change status to verified according to comment#2

Comment 6 errata-xmlrpc 2016-11-04 08:49:18 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://rhn.redhat.com/errata/RHBA-2016-2609.html