On Fedora 13 32bits open-vm-tools get all cpu and memory and freeze.
There's not enough information here to do anything.
. which version of open-vm-tools are you running?
. which VMware product are you running?
. what does "freeze" mean?
. what's the process that's using all the CPU?
. have you tried to enable logging and see if any useful information shows up?
I use packages from rpmfusion.
The version is: 126.96.36.1992 (build-243334)
We use ESX 3.5
The system freeze with kernel panic - Out of memory
The process that get all cpu: is vmtoolsd
No, this machine is production, and I can't stop this system to test with log.
You really shouldn't be using open-vm-tools in a production environment, since they're not officially supported by VMware. We always recommend you use the VMware Tools shipped with your VMware product.
Without any logs it's gonna be hard to know what's going on.
I agree, but the vmware-tools shipped with exx3.5 don't work with fedora, I turn off the open-vm-tools and the system work fine, what do you recommend? change fedora or exist other way to work with fedora?
To try to fix whatever problem you're running into, we'd at least need logs to know what's going on, since nobody in our internal QA has reported similar issues. It might be a problem with some patch Fedora may have applied, but again, without logs it will be really hard to figure out.
I don't generally follow updates for older releases of ESX, so I don't know how the distro support for ESX 3.5 is looking these days.
Without more information about what is going on (i.e., logs), there's nothing we can do.
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.