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.
Always. Tried 4 different times.
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 ***
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.
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.
Created attachment 442894 [details]
Created attachment 442895 [details]
Created attachment 442896 [details]
Just to make sure, the problem is that after clicking on "Configure Network", there is no eth0 in "Network Connections" dialog, right?
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
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:
Move to VERIFIED.
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.
(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
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.
*** This bug has been marked as a duplicate of bug 609784 ***