Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.4: Prevent repetitive system.log entries from Fusion Apps
Recently, while looking for something else in /var/log on my MacBook Pro, I happened to notice that the system log file was nearly 20MB in size -- yikes! By comparison, the log file on the Mac Pro was only 117KB. Clearly something was amiss. I opened Console, and found this in the system.log file:

...
Mar  6 19:35:47 tinisin kernel[0]: SMAC: FromHostIP: could not find IP 192.168.1.15 in lookup, so drop
Mar  6 19:35:48 tinisin kernel[0]: SMAC: FromHostIP: could not find IP 192.168.1.15 in lookup, so drop
Mar  6 19:35:49 tinisin kernel[0]: SMAC: FromHostIP: could not find IP 192.168.1.15 in lookup, so drop
...

Every second or so, that message appears...over and over and over. The IP address referenced is that of the same MacBook Pro, so I was really stumped. Off to the net, where I stumbled onto this thread at, of all places, the Ubuntu forums. It turns out that this problem is caused by the beta version of VMWare Fusion -- but only when connecting via AirPort. As posted in the referenced thread by Kalou, the solution involves a quick trip to Terminal:
/Library/Application\ Support/VMware\ Fusion/vmnet-apps.sh stop
As soon as I ran that command, the log file entries stopped appearing. When I launched VMWare Fusion again, all seemed fine -- my virtual machine restored successfully, and I was able to surf the net via the wireless connection. Even better, after quitting Fusion, the log entries did not start up again. As best I can tell, the shell script is responsible for running a DHCP server for Fusion (but that's mostly a guess).

If you're using Fusion over AirPort, it might be worth a quick glance at your system.log file to see if you're experiencing the same thing.
    •    
  • Currently 2.25 / 5
  You rated: 3 / 5 (4 votes cast)
 
[10,792 views]  

10.4: Prevent repetitive system.log entries from Fusion | 6 comments | Create New Account
Click here to return to the '10.4: Prevent repetitive system.log entries from Fusion' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Prevent repetitive system.log entries from Fusion
Authored by: hrbrmstr on Mar 07, '07 08:54:47AM

Confirmed this is a problem and confirmed this "fixes" it. I noticed this the other day and did the exact same thing. Tried posting to the VMware forums and wound up in an authentication loop. Didn't bother.

So, in terms of keeping score, Parallels betas: 1, VMware's betas: 0?


---
Mind the gap...



[ Reply to This | # ]
10.4: Prevent repetitive system.log entries from Fusion
Authored by: pottypigeon on Mar 07, '07 01:41:12PM

I might be wrong, but this shell script doesn't look to me as needing parameters.
By just launching it, it does what's expected.

My 2 euro-cents...



[ Reply to This | # ]
10.4: Prevent repetitive system.log entries from Fusion
Authored by: njvm on Mar 18, '07 10:22:01PM

Unfortunately, this solution did not work for me. I am using Beta 2 of Fusion. Running the command disables the error messages in the System log but then when I log-on to Fusion I have no network connectivity. Also, when I re-boot and open Fusion again everything is ok, eg I have network connectivity, but the error messages to the System log have again started up. Any ideas? I am using my Airport card to connect to the network.



[ Reply to This | # ]
10.4: Prevent repetitive system.log entries from Fusion
Authored by: tanjiee on Mar 21, '07 11:45:23PM
Bummer. The fact remains that even with the Fusion beta 2, the logging continues to be an issue. Something interesting I found in this Virtualization wiki http://wiki.osx86project.org/wiki/index.php/Virtualization

basically, they suggest that when not using vmware, we should run the command to stop the logging. I should notice that the command is a bit different. And, since I tried both, the following command actually works without giving error messges (cannot find.... type of error) The following is a direct quote from the page

When you're not using Fusion, stop the network kexts with

sudo '/Library/Application Support/VMware Fusion/boot.sh' --stop

and when you want to use Fusion again, resume the services with

sudo '/Library/Application Support/VMware Fusion/boot.sh' --start

You can also rotate the logs more frequently (so they don't have time to get as big), see the thread for details.

hope this helped someone

[ Reply to This | # ]
10.4: Prevent repetitive system.log entries from Fusion
Authored by: tanjiee on Mar 21, '07 11:48:46PM
Bummer. The fact remains that even with the Fusion beta 2, the logging continues to be an issue. Something interesting I found in this Virtualization wiki http://wiki.osx86project.org/wiki/index.php/Virtualization
basically, they suggest that when not using vmware, we should run the command to stop the logging. I should notice that the command is a bit different. And, since I tried both, the following command actually works without giving error messges (cannot find.... type of error) The following is a direct quote from the page

When you're not using Fusion, stop the network kexts with
sudo '/Library/Application Support/VMware Fusion/boot.sh' --stop

and when you want to use Fusion again, resume the services with

sudo '/Library/Application Support/VMware Fusion/boot.sh' --start

You can also rotate the logs more frequently (so they don't have time to get as big), see the thread for details.

hope this helped someone

[ Reply to This | # ]
10.4: Prevent repetitive system.log entries from Fusion
Authored by: njvm on Mar 22, '07 09:28:51PM

Excellent - thank you - works a treat.



[ Reply to This | # ]