Bug 833088 - Incorrect link status for NICs in VMs
Summary: Incorrect link status for NICs in VMs
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-18 14:45 UTC by Fabian Deutsch
Modified: 2012-06-18 15:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-18 15:03:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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


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