Your network adapter 'eth0' is not configured

it does depend on eth0 as part of its licensing validation.

Right - but the latest version of the 7.1 ISO uses Cent 6.4 - interfaces are labeled as em1, em2, etc out of the gate. 

Perhaps the software needs to look for em1 instead of eth0.

When you start the installation of the ISO, press tab and add "biosdevname=0" to the line. This will label the interfaces at eth0, eth1, etc.

good tip. I havent run accross the ISO naming the devices by their device name, I wonder if it depends on the hardware? I've been primarily using supermicro motherboards.

Thanks for the good advice, Carstman.

I am doing a test build from the 7.2 ISO (which appears to install Centos 6.5) on a Dell r610. My first attempt the interfaces all came up em1, em2, em3, em4. And just about everything I tried the system still complained about eth0 not being configured.

I hit Tab at the boot menu and added "biosdevname=0" to end of the line, then hit enter to start the install. Worked like a charm, eth0, eth1, eth2, eth3 once it was complete.

This PDF on the Dell website does a pretty good job of explaining what's going on. It appears the new Centos naming standard is in v6.1 and above. It's meant to reflect physical location of the interface, on the motherboard, on a card, etc. It also looks like the hardware has to be compliant to take advantage of the new system... looks like just about all the newer Dell Tx10, Rx10, Tx20 & Rx20 Poweredge servers are compliant.

http://linux.dell.com/files/whitepapers/consistent_network_device_namin…

I know that this happens on Dell hardware - we will look into dealing with this in the software. In the long run it will probably not matter with the introduction of a different licensing scheme

all you have to do, when building the iso, is add biosdevname=0 to the menu options under 'append' where the kernel is specified for that label.