Bug 646369 – [kvm] VIRT-IO NIC state is reported as 'unknown' on vm running over RHEL6 host

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 646369 - [kvm] VIRT-IO NIC state is reported as 'unknown' on vm running over RHEL6 host

Summary:	[kvm] VIRT-IO NIC state is reported as 'unknown' on vm running over RHEL6 host

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	kernel (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	rc
Target Release:	6.1
Assigned To:	jason wang
QA Contact:	Virtualization Bugs
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Depends On:
Blocks:	580954 649573 653340
	Show dependency tree / graph

Reported:	2010-10-25 05:13 EDT by Haim
Modified:	2014-01-12 19:47 EST (History)
CC List:	17 users (show)

See Also:
Fixed In Version:	kernel-2.6.32-84.el6
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Clones:	649573 (view as bug list)
Environment:
Last Closed:	2011-05-23 16:27:22 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2011:0542	normal	SHIPPED_LIVE	Important: Red Hat Enterprise Linux 6.1 kernel security, bug fix and enhancement update	2011-05-19 07:58:07 EDT

Groups: None (edit)

Description Haim 2010-10-25 05:13:19 EDT

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

Comment 2 Dor Laor 2010-10-28 05:11:18 EDT

we found an identical bug on a physical hardware (https://bugzilla.redhat.com/show_bug.cgi?id=635982

Comment 6 Dor Laor 2010-11-04 06:46:46 EDT

Jason, can we close this one since it's in the 5.5 kernel?

Comment 7 jason wang 2010-11-04 22:45:43 EDT

(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.

Comment 9 Dor Laor 2010-11-08 11:18:01 EST

(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?

Comment 10 jason wang 2010-11-09 00:46:37 EST

(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 13 Aristeu Rozanski 2010-12-13 10:09:22 EST

Patch(es) available on kernel-2.6.32-89.el6

Comment 17 Miya Chen 2011-02-24 01:58:21 EST

change it to verified based on comment#15

Comment 18 errata-xmlrpc 2011-05-23 16:27:22 EDT

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

Note You need to log in before you can comment on or make changes to this bug.