Busy system.log file

[dp_fusion]

This is a nearly continuous stream in the /var/log/system.log file - anyone know why this is happening?

Leopard, 10.5.2, this vm is OpenSuse 10.3.

Feb 29 22:09:24 wideglide kernel[0]: vmmon: host clock rate change request 0 -> 230

Feb 29 22:09:34 wideglide kernel[0]: vmmon: host clock rate change request 230 -> 0

Feb 29 22:09:34 wideglide kernel[0]: vmmon: host clock rate change request 0 -> 86

Feb 29 22:09:34 wideglide kernel[0]: vmmon: host clock rate change request 86 -> 267

Feb 29 22:09:45 wideglide kernel[0]: vmmon: host clock rate change request 267 -> 0

Feb 29 22:09:45 wideglide kernel[0]: vmmon: host clock rate change request 0 -> 66

Feb 29 22:09:45 wideglide kernel[0]: vmmon: host clock rate change request 66 -> 291

Feb 29 22:09:56 wideglide kernel[0]: vmmon: host clock rate change request 291 -> 0

Feb 29 22:09:56 wideglide kernel[0]: vmmon: host clock rate change request 0 -> 84

Feb 29 22:09:56 wideglide kernel[0]: vmmon: host clock rate change request 84 -> 353

Feb 29 22:10:07 wideglide kernel[0]: vmmon: host clock rate change request 353 -> 0

Feb 29 22:10:07 wideglide kernel[0]: vmmon: host clock rate change request 0 -> 135

Feb 29 22:10:07 wideglide kernel[0]: vmmon: host clock rate change request 135 -> 350

[dp_fusion]

Sorry I wasn't more clear - when I say near continuous stream I mean even when the VM is shut down and Fusion is off. Just about every 10 seconds or so. The only VM I've been using for some time is the OpenSuSE 10.3. And here's a picture of the activity monitor - mind you, fusion is off. Nearly 8% cpu?

[WoodyZ]

Sorry I wasn't more clear - when I say near continuous stream I mean even when the VM is shut down and Fusion is off. Just about every 10 seconds or so. The only VM I've been using for some time is the OpenSuSE 10.3. And here's a picture of the activity monitor - mind you, fusion is off. Nearly 8% cpu?

Sorry I don't have an answer to your original question that you started this thread for however I'm curious about what you said "And here's a picture of the activity monitor - mind you, fusion is off. Nearly 8% cpu?"... You say "Fusion is off" and while the Fusion UI Process (VMware Fusion) is not showing do you realize that the vmware-vmx process is a Running Virtual Machine? Are you Force Quitting the VMware Fusion UI in order to run a Virtual Machine Headless?

[dp_fusion]

I shut down the vm then I shut down Fusion. I don't know why that process is running. It's part of the mystery. I'm still exploring it too. I don't want to reboot and lose the forensics - I'm going to try a few things to see what turns up. I almost never shut down Fusion but did so to see if the logging would stop (it didn't). I'll post anything I learn.

Time marched on...

I restarted Fusion then each in turn I loaded my virtual machines, shutting them down before starting the next. The last one I loaded is the most previous vm I'd been running. It open in the usual suspended machine stupor with the big start button. Once it finished coming up I suspended it, shut it down. This time the vmx process was gone from the proc table, the logging stopped, and the CPU cooled down a bit. So there was a running (not suspended) vm (OpenSuSE) with no indication on the dock, and no running instance of Fusion. I wonder how that happened.

The logging problem is back but now only when the vm is unsuspended and running, so I'll try the syslog.conf changes next.

Edit: Changed the syslog config (its actually syslog-ng) and no difference, and shutting down syslog-ng offers no change - the problem remains. There are possibly some processes in SuSE that write directly to the console device - I know Solaris does this. I'll check the lsof output and see what has that device open, if anything.

Message was edited by: dp_fusion

[WoodyZ]

Have you tried reconnecting to the vmware-vmx process by starting Fusion then Run the target Virtual Machine and then shutdown (again) from within the Guest OS?

[dp_fusion]

Have you tried reconnecting to the vmware-vmx process by starting Fusion then Run the target Virtual Machine and then shutdown (again) from within the Guest OS?

Yes - just did and that part is back to normal (but still a mystery how it could have happened).