Bug 833088

Summary:	Incorrect link status for NICs in VMs
Product:	[Fedora] Fedora	Reporter:	Fabian Deutsch <fdeutsch>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	17	CC:	gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-18 15:03:12 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 Fabian Deutsch 2012-06-18 14:45:10 UTC

Description of problem:
The link status determined using ethtool is wrong for NICs in VMs (e.g. kvm VMs set up using virt-manager on stock F16 host).
virtio, e1000 and rtl81xx nic types are at least affected

Version-Release number of selected component (if applicable):
F16 host F17 guest

How reproducible:
Alway

Steps to Reproduce:
1. Setup F16 host, setup F17 guest
2. Ensure that the IF in question is not configured, so ifconfig … down the IF in question if neccessary
3. ethtool … reports link not connected
  
Actual results:
ethtool … reports link not connected

Expected results:
ethtool … should report connected (if it's connected to a bridge)

Additional info:
This is can also be observed on RHEV guests

Comment 1 Fabian Deutsch 2012-06-18 15:03:12 UTC

The interface has to be brought up before the link status can be checked:
$ ifconfig $IF up
$ ethtool $IF