Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#92 Out of memory and high cpu usage

v1.0 (example)
closed
nobody
guestd (12)
5
2011-01-28
2010-09-22
Kleber Rocha
No

On Fedora 13 32bits open-vm-tools get all cpu and memory and freeze.

Discussion

  • Marcelo Vanzin
    Marcelo Vanzin
    2010-09-22

    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?

     
  • Kleber  Rocha
    Kleber Rocha
    2010-09-22

    I use packages from rpmfusion.
    open-vm-tools-libs-0.0.0.243334-1.fc13.i686
    open-vm-tools-0.0.0.243334-1.fc13.i686
    akmod-open-vm-tools-0.0.0.243334-1.fc13.5.i686
    kmod-open-vm-tools-2.6.34.7-56.fc13.i686-0.0.0.243334-1.fc13.17.i686

    The version is: 8.4.1.1212 (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.

    Thanks

     
  • Marcelo Vanzin
    Marcelo Vanzin
    2010-09-22

    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.

     
  • Kleber  Rocha
    Kleber Rocha
    2010-09-22

    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?

    Thanks

     
  • Marcelo Vanzin
    Marcelo Vanzin
    2010-09-22

    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.

     
  • Marcelo Vanzin
    Marcelo Vanzin
    2011-01-14

    Without more information about what is going on (i.e., logs), there's nothing we can do.

     
  • Marcelo Vanzin
    Marcelo Vanzin
    2011-01-14

    • status: open --> pending
     
  • 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).

     
    • status: pending --> closed