I think that com.vmware.vcIntegrity is made from Vmware Update Manager.

I have disable VUM. When task VUM start for Update Signature --> start task for reconfiguring machine...

I am experiencing the same issue on my LINUX boxes only.  The "reconfigure" seems to "disconnect" the vNIC. Also, seems to be more prominant in the 64-bit systems using the E1000 vNIC.  Any thoughts?

--kev

I have also been having the same problem for the past 2 months.

The error messages are in fact due to the new VMware Update Manager feature in VC 2.5 (should be called a beta product in my opinion), and occur every time the service is started from the VC server, and also whenever a client adds the plugin to the VIC.

I originally thought those messages appeared on ALL of my VMs...this was not the case. Until reading this post I did not realize this issue was directly related to Linux. I have over 200 Linux VMs and after checking my recent task list, to my suprise, every VM that was reconfigured from com.vmware.vcIntegrity was either RHEL 4 or 5.

This has not caused any technical issues, but it definitely is very annoying to see (especially with 200+ messages).

This is the only thread I have seen on this issue, and I have not seen any reply from a VMware developer, so I am interesting in what they have to say.

I finally figured this one out! It was to do with the Flexible vs E1000 virtual network adaptor. Use the Flexible for 32-bit and E1000 for 64-bit. During VM creation, Vmware chooses the appropriate adapter depending on which OS you use. If you later decide to change this, you must first delete the old virtual network adapter, and add the new one. This will not be done automatically.

Update manager is trying to do something to update this configuration, and is not successful because the OS type is labelled incorrectly from the network adapter type. Because of this failure, the message "Reconfiguring Virtual Machine" from com.vmware.vcIntegrity repeats itself over and over again.

The moral of the story is to always make sure you pick the correct OS type before installing any Operating System (we've learned this the hard way). We had over 100 VMs created from a bad template (ouch!).

I can see it too - it seems GA-Deploy (guest agent) will only update the Red-Hat machines.

In the my log file I haven't any RH but in our production we have many of them and my RH administrator has asked, what is it. We then have disabled the VUM (didn't found any other way, check this: Vum, how can one avoid the atomatic install of guest agent on Red Hat linux? - although my method didn't work).

Has anyone deeper knowledge about it?

Reg

Christian

We have seen this exact issue as well, although it didn't cause any issues with any of our RHEL servers.  I am curious to see if anyone has a definite answer as to why this happens.

I had the same issue in VC Update2 this week..

VMware says it is a known issue...

Kb.vmware.com/kb/1008729