bringing up ethernet failed on 7 beta installed on VMware
i do not know how to configure network (ethernet) during installation of redhat 7 beta on a VMware (host system is Windows 7).
I thought after the installation was complete either Linux would automatically detect the ethernet during boot or i could use some network management tools after the system was up.
But i found from dmesg there is no ethernet detected by the kernel and from Applications on desktop there is no any networt
management tool available to use.
Should i re-install 7 beta and try to figure out how to configure network before installation starts?
Or is there any method i can use to bring up network on 7 beta?
The output of 'ifconfig' on my 7 beta follows.
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 0 (Local Loopback)
RX packets 1030 bytes 87752 (85.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1030 bytes 87752 (85.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 66:ea:e7:e0:f2:5f txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Thanks.
Responses
Did you install the VMware Tools on your Virtual Machine? Once the VM is running, run
lspci | grep -i net
To see if an adapter has been detected (even if dmesg doesn't report one). Also - depending on the setting you have selected for the adapter itself, it may have an impact. (i.e. if you selected replicate host device status and selected the ethernet device and you are using wireless on the host, it may not work). You can explicitly select a ethernet device (NAT, or direct or whatever). You may want to play with those settings.
After looking at some other threads, I had more questions: what version VMware Workstation are you using? Did you add an emulated or adapter, or VirtIO (or passthru). I run Fusion which likely does not handles devices quite the same. The lspci output will give us a better idea.
Also - someone else linked to the supported network devices
https://access.redhat.com/site/solutions/527083
I'd definately make sure the vmware tools is proper...
HOPEFULLY THIS IS JUST A MATTER OF REINSTALLING VMware Tools! I have had to re-install VMware tools numerous times in the past due to upgrades etc. If that is the case - hopefully you will not need the rest of what I wrote below!!
On vm systems, and starting with rhel 6 and above, make sure the MAC address in
/etc/udev/rules.d/70-persistent-net.rules file matches what is on the interface.
**Make note of the MAC address in /etc/udev/rules.d/70-persistent-net.rules for the specific interface
[root@yoursystem ~]# cd /etc/sysconfig/network-scripts
[root@yoursystem ~]# grep -i eth /etc/udev/rules.d/70-persistent-net.rules
Next, Determine which network interface should be up (do you have ifcfg-eth0 or ifcfg-em0?)
[root@yoursystem network-scripts] grep ONBOOT ifcfg* | grep -v ^\# | grep yes
Whichever interface the system claims is up - make a note of the HWADDR
[root@yoursystem network-scripts] grep HWADDR ifcfg* | grep -v ^\#
now go to the "edit properties" function in VMWare and click on the specific network interface (on your virtual system)
Questions for you: Does the MAC address AND the device "ifcfg-ethX" match what is in:
1) /etc/sysconfig/network-scripts/ifcfg-ethX (the one you identified a few lines up)
2) /etc/udev/rules.d/70-persistent-net.rules
3) The VMWare virtual NIC as shown in the "edit settings" hardware tab
**If /etc/udev/rules.d/70-persistent-net.rules shows your network interface should be (for example) ifcfg-eth1, then /etc/sysconfig/network-scripts/ifcfg-eth1 should 1) exist and 2) have the matching MAC address. This may sound like it would not apply, but I've seen it occur a number of times to be relevent enough to check if other simpler checks prove false.
If VMWare tools and the MACs and the devices all agree - this typically takes care of the consternation I have found with virtual systems.
- I've seen systems that have an "ifcfg-eth2" with the MAC address in the /etc/udev/rules.d/70-persistent-net.rules not match the device in /etc/sysconfig/network-s
cripts/ifcfg-ethX
-- example, the hardware address and interface in /etc/udev/rules.d/70-persistent-net.rules may show as 'ifcfg-eth1' when in /etc/sysconfig/network-scripts/ifcfg-eth0 EXISTS, but here is no /etc/sysconfig/network-scripts/ifcfg-eth1 - if that is the case (no ifcfg-eth1 file exists, but the file 70-persistent-net.rules file shows eth1 for that MAC), is copy the ifcfg-eth0 to ifcfg-eth1 and make the MAC address in ifcfg-eth1 match wht is in 70-persistent-net.rules match. Verify selinux contexts, and (if that is the case) disable completely ifcfg-eth0.
anyway, that scneario has occured more than a few times on some virtual systems I have had.
HOPEFULLY IT IS JUST A MATTER OF REINSTALLING VMWare tools!!!
Hi Kevin,
I've had something like this occur -
Check to see the output of lspci:
[root@yoursystem ~]# lspci | grep -i eth
Probably no output will generate.
Some immediate possible options:
1) Just for yuks, reinstall vmwaretools, however this time do it manually (attach the iso from the graphical vmware interface), hopefuly it is in/on one of your VMware data stores, otherwise burn it to a cdrom and attach the cdrom. Else, attach the iso using the graphical disk icon. Then, do a:
mkdir -p /mnt/notmounted /cdrom/notmounted;chmod 755 /cdrom
Then mount it and run the manual installation of vmware, (the automated vmware install can betray you silently):
[root@yoursystem ~]# mount /dev/cdrom /cdrom
[root@yoursystem ~]# ls /cdrom/ ## should show VMwaretools with some gz file
[root@yoursystem ~]# df -PhT # look for a place to put the small gz file
[root@yoursystem ~]# mkdir /tmp/vmwaretoolsdeleteafterwards/
[root@yoursystem ~]# rsync -au --progress /cdrom/ /tmp/vmwaretoolsdeleteafterwards/
[root@yoursystem ~]# cd /tmp/vmwaretoolsdeleteafterwards/
[root@yoursystem ~]# gunzip NAME-OF-GZIPP'D-VMWARE-TOOLS-FILE-GOES-HERE.gz
[root@yoursystem ~]# tar -xvf NAME-OF-TAR-VMWARE-TOOLS-FILE-GOES-HERE.tar
[root@yoursystem ~]# cd vmwaretools-distrib # I think
[root@yoursystem ~]# ./install.pl # I think
[root@yoursystem ~]# echo "TAKE ALL DEFAULTS"
[root@yoursystem ~]# echo "continue taking all defaults until it is complete"
[root@yoursystem ~]# echo "the initrd will be made at the end and the script should report as completed"
[root@yoursystem ~]#
[root@yoursystem ~]# lspci | grep -i eth
[root@yoursystem ~]# echo "hopefully you get some output on your devices"
[root@yoursystem ~]# echo "reboot the box and if needed, upgrade the 'virtual hardware' of the system while the system is down"
[root@yoursystem ~]# echo "after reboot, go to the /etc/sysconfig/network-scripts and see if ifcfg-ethX files exist, else remove existing interfaces and install new virtual NIC"
Hope this helps
- It seems you already have VMware tools if you're getting that error regarding kernel-headers etc...
- The VMware tools is often packaged as yet another iso buried within the overarching VMware tools download.
- However, this link might help you get the proper iso mounted, link at VMware.com
- I believe you can extract VMware tools from the free ESXi product they let you download (I we did that once).
- Can you log into VMware.com's website and download VMware tools? They typically do not disallow the mere download of VMware-tools.
- Also see this link at vmware.com
Kevin,
Do you happen to have a snapshot for the system under VMware for the system prior to the changes that were made? (or did the interface ever work)?
That bit you describe above happened to me a while back as well and I believe I had to install the following: kernel-headers, kernel-devel, glibc and gcc..
- Make a local yum repo with your RHEL 7 disk - scroll down to paragraph 5.5.6.. Attach the DVD or RHEL 7 iso to the system and create a local yum repo.
- You might need the following three rpms. You will have to find them on your RHEL 7 DVD.
mkdir /cdrom
chmod 755 /cdrom
mount /dev/cdrom /cdrom
rsync -au --progress /cdrom/ /path/to/a/directory/with/enough/space/local/yum/
cd /to/the/path/to/your/local/yumrepo/
echo "cd to the directory with the below packages"
echo "look around in the directories in the yum repo location for these files."
rpm -ivh deltarpm-VERSION python-deltarpm-VERSION createrepo-VERSION
createrepo -v /path/to/your/local/yumrepo
Properly edit your /etc/yum.repos.d/local.repo file
According to this VMware video, you must have glibc and gcc along with kernel-headers and kernel-devel. So a yum repo will help get these rpms and their dependencies.
After you create the local yum repo and install the rpms, try the install of vmwaretools (manually) again.
Good luck,
Rem
Kevin,
Above your post, I recommended installing manually with the three needed files with the rpm command so you can use 'createrepo' (it has three total rpms you must install simultaneously).
SEE THE POST DIRECTLY ABOVE YOURS - the one I made on Feb 20th, just before yours you made on FEB 21st
ALSO - you may need to temporarily disable the existing repo files in /etc/yum.repos.d/ (anything with a ".repo" extension). MAKE NOTE OF ANY CHANGES YOU MAKE TO WHICH FILES.
You can tar up the files as a backup
cd /etc/yum.repos.d/
tar cvf yumfiles_backup.tar ./*
vi the files and look for "enabled=1" (except for the LOCAL yum repo, leave that one enabled), and disable by changing to "enabled=0".
MAKE A BACKUP TAR FILE FIRST ABOVE!!!
Kevin,
I happened to have a very minimalistic server with no kernel-devel, kernel-headers, gcc, or glibc.
This may be the dependencies - just make your yum repo and install the rpms.
[root@testvictim1 ~]# yum install kernel-headers kernel-devel glibc gcc
Resolving Dependencies
---output truncated---
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
gcc x86_64 my-repo 10 M
Installing for dependencies:
cloog-ppl x86_64 my-repo 93 k
cpp x86_64 my-repo 3.7 M
glibc-devel x86_64 my-repo 978 k
glibc-headers x86_64 my-repo 608 k
libgomp x86_64 my-repo 118 k
mpfr x86_64 my-repo 156 k
ppl x86_64 my-repo 1.3 M
Transaction Summary
================================================================================
Install 8 Package(s)
Total download size: 17 M
Installed size: 36 M
Is this ok [y/N]: n
Exiting on user Command
[root@testvictim1 ~]#
So those are the dependencies you'd need for glibc and gcc.
If you happened to have a snapshot for your VMware system, that could be a saving feature in this scenario.
Always reboot after installing glibc...
Kevin, install the three rpms using the rpm command in the notes I mentioned above and make the yum repo
I made instructions to create a localized yum repo with your rhel 7 disk and posted it previously (above).
You can manually install (again, with the rpm command) the needed three rpms to be able to run 'createrepo' - instructions above in the replies.
From there, you can then install kernel-headers and the other discussed rpms (see discussions above), and then get vmware tools installed.
In order for me to get this working I had to add the following line to the vmdk file for the VM.
ethernet0.virtualDev = "e1000"
Afterward you remove the VM and re-add it. Following the directions provided by Remmele and then this last step got it all sorted out for me.
Kevin,
I had the same problem with the kernel headers, try
yum install kernel-headers-`uname -r` kernel-devel-`uname -r`
then the header path is something like this : "/lib/modules/3.10.0-123.el7.x86_64/build/include"
It would be good if we could fork this topic on the forum as I ran into the same problem with the ifconfig command however it was easily solved with net-tools.
modified the VMware's virtual host configuration file like this ****.vmx and add new line :
ethernet0.present = "TRUE"
ethernet0.connectionType = "nat"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet0.addressType = "generated"
add a new line: ethernet0.virtualDev = "e1000"
ethernet0.present = "TRUE"
ethernet0.connectionType = "nat"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet0.addressType = "generated"
ethernet0.virtualDev = "e1000"
Do it after shutdown the vpc.