Bug 757286 - Fedora doesn't properly disable "Consistent Network Device Naming" when HVM virtualized
Summary: Fedora doesn't properly disable "Consistent Network Device Naming" when HVM v...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: biosdevname
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Narendra K
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-26 06:48 UTC by Edward Z. Yang
Modified: 2012-08-07 17:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 855466 (view as bug list)
Environment:
Last Closed: 2012-08-07 17:28:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Edward Z. Yang 2011-11-26 06:48:21 UTC
Steps to reproduce:
1. Boot Fedora as an HVM
2. Look at /dev

Expected Behavior: eth0 is your network device (as specified by the hypervisor), as per https://bugzilla.redhat.com/show_bug.cgi?id=673268

Actual Behavior: p3p1 is your network device, as Fedora does device naming as per http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming

It's a little nontrivial to figure out if you're running as HVM, but you can probably figure it out looking at ACPI, for example:

     httpd@vm-6858:~/lab$ dmesg | grep paravirt
     [    0.000000] Booting paravirtualized kernel on KVM
     [    0.000000] ACPI: RSDP 000fdab0 00014 (v00 BOCHS )
     [    0.000000] ACPI: RSDT 1fffdc40 00034 (v01 BOCHS  BXPCRSDT 00000001 BXPC 00000001)
     [...]

     From the same disk image, except running inside HVM:
     [    0.000000] Booting paravirtualized kernel on bare hardware
     [    0.000000] ACPI: RSDP 000ea010 00024 (v02    Xen)
     [    0.000000] ACPI: XSDT 0fff8b70 00034 (v01    Xen      HVM 00000000 HVML 00000000)
     [...]

The vendor probably has reasonable information. Try also /sys/class/dmi/id/product_name /sys/class/dmi/id/product_version /sys/class/dmi/id/sys_vendor

Let us know if the bug component classification is wrong.

Comment 1 Fedora End Of Life 2012-08-07 17:28:27 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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