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 913425

Summary:	use set_link to change rtl8139 and e1000 network card's status but fail to make effectively after reboot guest
Product:	Red Hat Enterprise Linux 7	Reporter:	Qian Guo <qiguo>
Component:	qemu-kvm	Assignee:	jason wang <jasowang>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	acathrow, akong, areis, bsarathy, chayang, flang, hhuang, jasowang, juzhang, michen, mkenneth, mst, qiguo, qzhang, rhod, sluo, stefanha, tlavigne, virt-maint
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	890288	Environment:
Last Closed:	2013-11-04 07:08:49 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:
Bug Depends On:	890288
Bug Blocks:	907397, 907716

Comment 3 jason wang 2013-08-30 05:40:48 UTC

Please retest the recent qemu-kvm, it should have been fixed.

Comment 4 Qian Guo 2013-08-30 07:15:51 UTC

Test this bug with following components:
# rpm -q qemu-kvm
qemu-kvm-1.5.3-2.el7.x86_64

Steps:
1.boot guest with rtl8139/e1000/virtio_net nic device.
eg:...-netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:33:1a:04 ...
2.check nic status in guest(default: 'up').
# cat /sys/class/net/eth0/operstate 
up
3.change nic status in monitor.
(qemu) set_link $network_device off
4.re-check nic status in guest.
# cat /sys/class/net/eth0/operstate 
down
5.reboot guest and recheck nic status.
# cat /sys/class/net/eth0/operstate
down

Test this w/ all vnic devices, after reboot, the network status are all down, so according to above, this bug is fixed by qemu-kvm-1.5.3-2.el7.x86_64.

Comment 5 jason wang 2013-11-04 07:08:49 UTC

Close this according to Comment #4. It has been fixed.