Bug 833088 - Incorrect link status for NICs in VMs
Incorrect link status for NICs in VMs
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
17
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-18 10:45 EDT by Fabian Deutsch
Modified: 2012-06-18 11:03 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-18 11:03:12 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Fabian Deutsch 2012-06-18 10:45:10 EDT
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 11:03:12 EDT
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.