Red Hat Bugzilla – Bug 123420
Permanent fix for known network problem in VMware.
Last modified: 2014-03-16 22:45:13 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6)
Description of problem:
As stated in
is a known problem with the check_link_down function when Fedora is
run from within VMware. I've created a fix (attached) for this problem
that can be included permanently in the code.
The effect: if (this is VMware) then do as described in the Vmware FAQ
else do what is normal for all other systems.
The detection of VMware I wrote is based on the fact that the newer
VMware versions have an SMBIOS that can be read using dmidecode. All I
do is check if the term vmware is present in the output or not.
I've tested this with Vmware 4.5.1 and it works fine for me.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install VMware 4.5
2. Install Fedora inside vmware with DHCP
3. Network fails to come up with "Determining IP information for
eth0... failed; no link present. Check cable?"
Actual Results: No usable network connection.
Expected Results: Usable network connection.
This fix is probably related to bug 85537
Although VMware is not mentioned, this is the exact type of network
adapter VMware emulates and also the exact same error message.
Created attachment 100296 [details]
Proposed patch for /etc/sysconfig/network-scripts/network-functions
I just found out that Fedora Core 2 has been released. I tested it and
the reported problem has been resolved in FC2.
I'm closing this bug report.
Perhaps the mentioned bug 85537 can be closed aswell.