Bug #1023

FREECPU=0 prevents scheduler to allocate VM

Added by rudolf strijkers almost 9 years ago. Updated over 8 years ago.

Status:ClosedStart date:12/07/2011
Priority:NormalDue date:
Assignee:Javi Fontan% Done:


Category:Core & System
Target version:Release 3.2
Resolution:fixed Pull request:
Affected Versions:OpenNebula 3.0


The FREECPU variable is calculated from top information collected in kvm.rb. The parsing, however, fails and the value remains unset.

$ top -v
procps-ng version 3.3.0

$ uname -a
Linux mike 3.1.0-1-amd64 #1 SMP Tue Nov 29 13:47:12 UTC 2011 x86_64 GNU/Linux

$ cat /etc/debian_version

A quick fix is attached. Though trivial, further investigation is necessary to ensure correct parsing of top's output.

patch.txt Magnifier (831 Bytes) rudolf strijkers, 12/07/2011 01:38 PM

Associated revisions

Revision 14579991
Added by Javi Fontan over 8 years ago

bug #1023: fix host cpu retrieval for procps-ng


#1 Updated by Ruben S. Montero almost 9 years ago

  • Target version set to Release 3.2
  • Resolution deleted (worksforme)

#2 Updated by Ruben S. Montero almost 9 years ago

  • Status changed from New to Assigned
  • Assignee set to Javi Fontan

#3 Updated by Javi Fontan over 8 years ago

  • Status changed from Assigned to Closed
  • Resolution set to fixed

Thanks for the patch! I've uploaded a version than works with both procps and procps-ng

Also available in: Atom PDF