RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 592071 - Installing rhel6 to KVM VM does not detect vm's network card
Summary: Installing rhel6 to KVM VM does not detect vm's network card
Keywords:
Status: CLOSED DUPLICATE of bug 609784
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: All
OS: Linux
low
high
Target Milestone: rc
: ---
Assignee: Radek Vykydal
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-13 19:23 UTC by Steve Grubb
Modified: 2013-01-09 22:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-07 13:59:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
log (35.03 KB, text/plain)
2010-09-03 13:20 UTC, Steve Grubb 		no flags Details
syslog (27.53 KB, text/plain)
2010-09-03 13:20 UTC, Steve Grubb 		no flags Details
eth0 (73 bytes, text/plain)
2010-09-03 13:21 UTC, Steve Grubb 		no flags Details
View All

Description Steve Grubb 2010-05-13 19:23:20 UTC 
Description of problem:
Using beta1 and just tested on snap4, it is not detecting network cards when installing as a KVM virtual machine. I am using a fully updated F-12 machine and installing the DVD rhel6 server image through the Virtual Machine Manager. When I get to the screen that has a "Configure Network" button and click on it, it shows no wired cards. Looking at the view|Details menu item on the Virtual Machine shows a NIC with a MAC address.

After the newly installed vm reboots, networking is enabled but eth0 is not up. The install did make an ifcfg-eth0 file, but ONBOOT=no and BOOT_PROTO=dhcp is completely missing.

Version-Release number of selected component (if applicable):
whatever is in snap4.

How reproducible:
Always. Tried 4 different times.
Comment 1 Radek Vykydal 2010-05-14 08:52:02 UTC 
This should be fixed in snap 5, you can see https://bugzilla.redhat.com/show_bug.cgi?id=520146#c45 for detailed info.

*** This bug has been marked as a duplicate of bug 520146 ***
Comment 2 Steve Grubb 2010-09-03 12:34:01 UTC 
This bug still exists with the RC from Sept 1. Installation on F-13 KVM system leaves no network cards detected. This time instead of minimal install, I do a basic server install.
Comment 3 Radek Vykydal 2010-09-03 13:06:00 UTC 
Can you please attach /var/log/anaconda.log, /var/log/anaconda.syslog from installed system?
Also either contents of /etc/sysconfig/network-scripts/ifcfg-eth* from installed system, or /tmp/ifcfg.log gathered at the end of installation will be helpful.
Comment 4 Steve Grubb 2010-09-03 13:20:17 UTC 
Created attachment 442894 [details]
log
Comment 5 Steve Grubb 2010-09-03 13:20:51 UTC 
Created attachment 442895 [details]
syslog
Comment 6 Steve Grubb 2010-09-03 13:21:19 UTC 
Created attachment 442896 [details]
eth0
Comment 7 Radek Vykydal 2010-09-03 14:16:20 UTC 
Just to make sure, the problem is that after clicking on "Configure Network", there is no eth0 in "Network Connections" dialog, right?
Comment 8 Dor Laor 2010-09-05 20:31:36 UTC 
Is that unique for virtio NIC ? What happens when e1000 or rtl8139 are used?
Any idea what's the root-cause? If anaconda is the faulty one it shouldn't happen for VMs only
Comment 9 yanbing du 2010-09-06 08:40:00 UTC 
Host F-13, guest rhel6-RC, do not meet the bug.
When click "Configure Network" button, the "Network Connections" dialog come out and can edit eth0 well with no problem.
Relative packages' version as following:
kernel-2.6.33.8-149.fc13.x86_64
libvirt-0.8.2-1.fc13.x86_64
qemu-kvm-0.12.5-1.fc13.x86_64
qemu-img-0.12.5-1.fc13.x86_64
python-virtinst-0.500.4-1.fc13.noarch
virt-manager-0.8.5-1.fc13.noarch

Move to VERIFIED.
Comment 10 Steve Grubb 2010-09-07 13:03:11 UTC 
The problem is that no network is configured by default. Eth0 is there with the hw mac address, but its set to "no" for onboot. So, this means you cannot get into the machine after installing it except by the console. The series of dialogs also don't route me into anything where a network card might be configured, so maybe its not detecting one? Moving back out of VERIFIED because installing a system does not setup a network card that is usable from a guest.
Comment 11 Radek Vykydal 2010-09-07 13:24:38 UTC 
(In reply to comment #10)
> The problem is that no network is configured by default.

This an issue different from that given in your bug Description, which is _detection_ of the card, and which is fixed. Your present problem is probably duplicate of bug 609784, see https://bugzilla.redhat.com/show_bug.cgi?id=609784#c17
Comment 12 Steve Grubb 2010-09-07 13:48:11 UTC 
The description in comment #0 paragraph 2 is still the same. onboot="no" is what's written making networking unusable until a sysadmin intervenes. This is different than RHEL5 behavior. If this is an intentional design change, then I guess tech notes are appropriate.
Comment 13 David Cantrell 2010-09-07 13:59:31 UTC 

*** This bug has been marked as a duplicate of bug 609784 ***
Note You need to log in before you can comment on or make changes to this bug.