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.
Description of problem:
using VIRT-IO NIC, it seems as if its state is reported as 'unknown' instead of its real state (up, down).
How do I see it?
1) rhel6 host running guest with VIRT-IO network device
2) on guest machine, run the following command:
- cat /sys/class/net/eth0/opersatate = unknown
versions:
2.6.32-71.el6.x86_64
libvirt-0.8.1-27.el6.x86_64
vdsm-4.9-20.2.x86_64
device-mapper-multipath-0.4.9-30.el6.x86_64
lvm2-2.02.72-8.el6.x86_64
qemu-kvm-0.12.1.2-2.113.el6.x86_64
iptables-1.4.7-3.el6.x86_64
(In reply to comment #6)
> Jason, can we close this one since it's in the 5.5 kernel?
Please don't, I also find a state initialization issue with RHEL6/upstream, have sent patch upstream and wait for them to be applied.
(In reply to comment #7)
> (In reply to comment #6)
> > Jason, can we close this one since it's in the 5.5 kernel?
>
> Please don't, I also find a state initialization issue with RHEL6/upstream,
> have sent patch upstream and wait for them to be applied.
Upstream qemu-kvm or netdev? Can you please share the patch?
(In reply to comment #9)
> (In reply to comment #7)
> > (In reply to comment #6)
> > > Jason, can we close this one since it's in the 5.5 kernel?
> >
> > Please don't, I also find a state initialization issue with RHEL6/upstream,
> > have sent patch upstream and wait for them to be applied.
>
> Upstream qemu-kvm or netdev? Can you please share the patch?
Netdev and wait for applied.
Comment 13Aristeu Rozanski
2010-12-13 15:09:22 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2011-0542.html
Description of problem: using VIRT-IO NIC, it seems as if its state is reported as 'unknown' instead of its real state (up, down). How do I see it? 1) rhel6 host running guest with VIRT-IO network device 2) on guest machine, run the following command: - cat /sys/class/net/eth0/opersatate = unknown versions: 2.6.32-71.el6.x86_64 libvirt-0.8.1-27.el6.x86_64 vdsm-4.9-20.2.x86_64 device-mapper-multipath-0.4.9-30.el6.x86_64 lvm2-2.02.72-8.el6.x86_64 qemu-kvm-0.12.1.2-2.113.el6.x86_64 iptables-1.4.7-3.el6.x86_64