vmnet: Setting peer info for hub:

[JoostvanVoorst]

Crew,

My logs on my MacBook Pro are flushed with the follwing lines:

3/2/11 15:44:48     kernel    vmnet: Setting peer info for hub: 0, port: 1, rcv: TRUE, flags: 32835
3/2/11 15:44:48     kernel    vmnet: Setting peer info for hub: 0, port: 1, rcv: TRUE, flags: 32835
3/2/11 15:44:48     kernel    vmnet: Setting peer info for hub: 0, port: 1, rcv: TRUE, flags: 32835
3/2/11 15:45:11     kernel    vmnet: Setting peer info for hub: 0, port: 1, rcv: TRUE, flags: 67
3/2/11 15:45:11     kernel    vmnet: Setting peer info for hub: 0, port: 1, rcv: TRUE, flags: 67
3/2/11 15:45:11     kernel    vmnet: Setting peer info for hub: 0, port: 1, rcv: TRUE, flags: 67

Thousend of lines in only a few hours. Can someone tell me what this means? Those thousend of lines of logs do not seem right to me.

Regards,

Joost

Model Name:    MacBook Pro
Model Identifier:    MacBookPro6,2
Memory:    8 GB

Mac OS X 10.6.6.

VMware Fusion Version 3.1.2 (332101)

[WoodyZ]

I believe those messages are normal and to be expected and have to do with VMware Networking, and the ones you're showing me tells me your using a Bridged Network on the VM that created those messages.  You'll see a set of messages like that when starting and shutdown a VM and hub: 0 is for Bridged, hub: 1 is for Host Only and hub: 8 is for NAT.  If you've added a custom VMnets the number will be that which you assigned.

[JoostvanVoorst]

WoodyZ, thank you for your answer. Are you not surprised by the vast amount of log lines? There are literally thousand of lines in just a few hours. So it is not just a few lines of log while booting a VM or while shutting down. It is a continuous flow of these messages.

I'm running spaces where my VM is designated to space 2. So I can easily swap between OS X and my WIN7 VM using a shortcut key. Do you think it is possible that the logs are created every time I swap from and to my VM?

Message was edited by: JoostvanVoorst (Typo)

[Mikero]

You could test that by opening the log in Console, setting a marker and then seeing what you can do to generate the log 'spew'.

If there's something we can reproduce, I can get a bug filed.

[WoodyZ]

Are you not surprised by the vast amount of log lines? There are literally thousand of lines in just a few hours. So it is not just a few lines of log while booting a VM or while shutting down. It is a continuous flow of these messages.

To be honest when you mentioned the quantity of lines in your OP I dismissed it a an intentional exaggeration however if you are literally seeing thousands of lines in a few hours from one Virtual Machine then I'd consider it a real issue and it would have been nice if Mikero would have quantified what it a normal amount however I can tell you that I'm not seeing the same behavior you are although I'm now going to monitor the kernel log more closely now.

I'm running spaces where my VM is designated to space 2. So I can easily swap between OS X and my WIN7 VM using a shortcut key. Do you think it is possible that the logs are created every time I swap from and to my VM?

I checked the log while switching Spaces with a Virtual Machine in Full Screen view and it was not writing to the log.

IMO Any program that is making excessive writes to a log file, except when in debug mode, is an indication of an issue that needs to be addressed.

I'd open a Service Request on this issue and go from there.

[JoostvanVoorst]

Gentlemen, WoodyZ, Mikero,

Thank you for your input. I have put a marker in my kernel.log and started VMware Fusion, then I started my WIN7 VM, logged on to our domain and started MS Outlook to generate some network traffic. 7 minutes later I added an other marker in my kernel.log. Please find those lines below. I did change the NIC in the VM back to bridged mode (auto detect) my preferred way of working on the domain. (You might see this in the log lines below)  I could not see any relation between the logs spew and me switching spaces (switching between Finder and my VM). Please let me know if I need to submit more/other logs or if you want to have me run more tests.

N.B. before starting this thread I've rebooted my machine, uninstalled and re-installed VMware Fusion.

Regards,

Joost

Thursday, March 3, 2011 08:13:17  Europe/Amsterdam

Mar  3 08:13:50 username kernel[0]: vmmon: PTSC: initialized at 2660325000 Hz using reference clock

Mar  3 08:13:50 username kernel[0]: vmmon: Cycles 51

Mar  3 08:13:52 username kernel[0]: vmci: Open socket 0x1bcce950.

Mar  3 08:14:42 username kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x1b95bc00.

Mar  3 08:14:42 username kernel[0]: vmnet: VMNetConnect: returning port 0x1b95bc00

Mar  3 08:14:42 username kernel[0]: vmnet: Setting peer info for hub: 8, port: 3, rcv: TRUE, flags: 64

Mar  3 08:14:42 username kernel[0]: vmnet: VMNET_SO_BINDTOHUB: port: paddr 00:50:56:fb:8f:2b

Mar  3 08:14:42 username kernel[0]: vmnet: Hub 8

Mar  3 08:14:42 username kernel[0]: vmnet:     Port 0

Mar  3 08:14:42 username kernel[0]: vmnet:     Port 1

Mar  3 08:14:42 username kernel[0]: vmnet:     Port 2

Mar  3 08:14:42 username kernel[0]: vmnet:     Port 3

Mar  3 08:14:42 username kernel[0]: vmnet: Setting peer info for hub: 8, port: 3, rcv: TRUE, flags: 64

Mar  3 08:14:42: --- last message repeated 2 times ---

Mar  3 08:14:42 username kernel[0]: vmnet: Setting peer info for hub: 8, port: 3, rcv: TRUE, flags: 32835

Mar  3 08:14:50 username kernel[0]: vmnet: Setting peer info for hub: 8, port: 3, rcv: TRUE, flags: 64

Mar  3 08:14:50: --- last message repeated 1 time ---

Mar  3 08:14:50 username kernel[0]: vmnet: VMNetDisconnect called for port 0x1b95bc00

Mar  3 08:14:50 username kernel[0]: vmnet: Invalidating peer info for hub: 8, port: 3

Mar  3 08:14:50 username kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x1b95bc00.

Mar  3 08:14:55 username kernel[0]: port: 1, rcv: TRUE, flags: 67

Mar  3 08:14:55 username kernel[0]: vmnet: Setting peer info for hub: 0, port: 1, rcv: TRUE, flags: 67

Mar  3 08:14:55: --- last message repeated 6 times ---

Mar  3 08:14:55 username kernel[0]: vmnet: Setting peer info for hub: 0, port: 1, rcv: TRUE, flags: 32835

Mar  3 08:15:20: --- last message repeated 24 times ---

Mar  3 08:15:20 username kernel[0]: vmnet: Failed to deep copy mbuf: 12.

Mar  3 08:15:20 username kernel[0]: vmnet: bridge-en0: SendToVNet copy failed: 12.

Mar  3 08:19:46 username kernel[0]: flags: 67

Mar  3 08:19:46 username kernel[0]: vmnet: Setting peer info for hub: 0, port: 1, rcv: TRUE, flags: 32835

Mar  3 08:20:16: --- last message repeated 28 times ---

Mar  3 08:20:16 username kernel[0]: port: 1, rcv: TRUE, flags: 32835

Mar  3 08:20:16 username kernel[0]: vmnet: Setting peer info for hub: 0, port: 1, rcv: TRUE, flags: 67

Mar  3 08:20:16: --- last message repeated 7 times ---

Mar  3 08:20:16 username kernel[0]: vmnet: Setting peer info for hub: 0, port: 1, rcv: TRUE, flags: 32835

Mar  3 08:20:46: --- last message repeated 24 times ---

Thursday, March 3, 2011 08:21:07  Europe/Amsterdam