After installing a couple of Mac OS X 10.5.6 Software Updates today:
- Security Update 2009-001
- Java for Mac OS X 10.5 Update 3
I received “The network bridge on device /dev/vmnet0 is not running.” error in VMware Fusion v2.0.2 (147997) when I tried to restore my Fedora 10 VM. The Google search produced some interesting results but nothing worked. I reinstalled Fusion and the dialog went away but network bridging still did not work. I then uninstalled and then installed Fusion and the same result. I rebooted my XP VM and it doesn’t have network connectivity either.
What finally did work was to uninstall Fusion and follow the manual uninstall procedures here. Then after a clean install network bridging is working again.
I used VMware’s instructions to install VMware Tools (VMwareTools-7.9.3-147997.tar.gz from VMware Fusion v2.0.2 (147997)) in Fedora 10 using the “Installing VMware Tools from the Command Line with the Tar Installer” section. For the most part I feel that I was successful. I can copy/paste and the system time updates coming out of standby which it never did before under Fedora 8.
I am having to reconnect the NIC manually coming out of standby. SELinux mechanism is firing and seemingly the cause of the problem. I don’t have a solution.
One example is: SELinux prevented mount from mounting on the file or directory “/usr/lib/vmware-tools/sbin32/vmware-hgfsmounter” (type “lib_t”) when I went into suspend and came out. I issued the fix command explained in “settroubleshoot browser”. It did take a few moments to complete.
Another example is: SELinux is preventing ifconfig (ifconfig_t) “read” to /var/run/vmware-active-nics (initrc_var_run_t). This file does not exist. I suspect this file exists when it comes out of standby but then gets deleted after the NICs are re-activated.
Before installing VMware Tools, I was able to boot with no problem. Now when I boot the POST screen has two issues:
- Mounting local filesystems: FAILED
- Mounting HGFS shares: FAILED (This one is under “Starting VMware Tools services in the virtual machine:”). I solved this problem by sharing a folder with my Mac from the Fusion Settings dialog for the Virtual Machine.
Between my install of Boa on Fedora 8 and today’s install of Boa “boa-0.94.14-0.10.rc21.fc9 (i386)” in Fedora 10 a bug was introduced into the /etc/boa.conf file. At some point they changed the location of the /srv/www/boa directory to /var/www/boa. They forgot to update the ScriptAlias value in /etc/boa.conf. Just change the svn in the path to var and then restart boa. CGI scripts in that location will start working again.
Musings of a software engineer in Silicon Valley