Bug #10779: Memory detection of Xen hosts is incorrect - Rudder - Issue Tracker

Custom queries

8.1 beta
Bugs triage
My TR
Need technical review
Open bugs (all)
Open bugs (UI - UX)
Open UX defects (all)
Opened by users

Actions

Copy link

Bug #10779

open

Memory detection of Xen hosts is incorrect

Added by Florian Heigl almost 7 years ago. Updated 7 days ago.

Status:

New

Priority:

N/A

Assignee:

Category:

Web - Nodes & inventories

Target version:

7.3.15

Pull Request:

Severity:

Minor - inconvenience | misleading | easy workaround

UX impact:

User visibility:

Operational - other Techniques | Rudder settings | Plugins

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

Fusion Inventory seems to only look at /proc/meminfo to detect the memory a Xen host has.

That will reflect the memory assigned the dom0 - likely 2-16GB, whereas all the other ram is managed by the hypervisor.
The problem here is that Rudder uses that to fill the field named "Total physical memory (RAM)"

That is wrong. Total physical memory is obtained only via xl info | grep total_memory (newer systems) or xm info | grep total_memory (old systems)

It matters, really:
In my example server the difference between the two is just about 990GB.

That way you can't apply any rule-based tuning profiles (not that I have one yet, but not that I could have one, either ;-)

History
Notes
Property changes

Actions

Copy link

Updated by François ARMAND almost 7 years ago

Related to Bug #10787: Xen domU detection issues with pvops kernels. added

Actions

Copy link

Updated by François ARMAND almost 7 years ago

Related to deleted (Bug #10787: Xen domU detection issues with pvops kernels.)

Actions

Copy link

Updated by François ARMAND almost 7 years ago

Priority changed from 0 to 35

Thanks for reporting.

What are the value(s) reported in hardware > memory?

Actions

Copy link

Updated by Janos Mattyasovszky almost 7 years ago

Nope.

Node Summary -> Node characteristics -> General -> Total physical memory (RAM): 9.08 GB

The dom0 has memory like:

# free -m
             total       used       free     shared    buffers     cached
Mem:          9298       5482       3815        457         28       4328
-/+ buffers/cache:       1125       8172
Swap:        32767          2      32765

The system has memory like:

# xl info 2>&1 | grep memory
total_memory           : 1048467
free_memory            : 998984

Here we see: 9298/1024 = 9.08, which is definetly not "Total physical memory", but "Total OS memory"

Actions

Copy link

Updated by François ARMAND almost 7 years ago

Yes, it is defenitly os memory, not physical memory. Fusion inventory is not correctly labeling the memory reported (it is in tag <HARDWARE><MEMORY>), and that we (dumbly) used the same term.

Do you have defferent information in Node Summary -> Node characteristics -> hardware > memory, where you should have "memory slots"? I'm almost sure it will be the same as os memory, though.

Actions

Copy link

Updated by Benoît PECCATTE almost 7 years ago

Priority changed from 35 to 50

Actions

Copy link

Updated by Florian Heigl over 6 years ago

Priority changed from 50 to 49

Sorry I had missed your feedback request. Will check.

Actions

Copy link

Updated by Florian Heigl over 6 years ago

Hi,

the memory slots are correctly detected...

Number of slots is correct (96)
and it also knows in which slot modules are installed.
A sum is not available.

I would much prefer if the correct number was obtained based on the xl/xm info output.
less effort on all ends and not relying on dmidecode (at least on ARM that matters!)

Actions

Copy link

Updated by Benoît PECCATTE over 6 years ago

Priority changed from 49 to 47

Actions

Copy link

#10

Updated by François ARMAND over 5 years ago

Target version set to 4.3.8
Priority changed from 47 to 0

Actions

Copy link

#11

Updated by Vincent MEMBRÉ over 5 years ago

Target version changed from 4.3.8 to 4.3.9

Actions

Copy link

#12

Updated by Alexis Mousset over 5 years ago

Target version changed from 4.3.9 to 4.3.10

Actions

Copy link

#13

Updated by François ARMAND about 5 years ago

Target version changed from 4.3.10 to 4.3.11

Actions

Copy link

#14

Updated by Vincent MEMBRÉ about 5 years ago

Target version changed from 4.3.11 to 4.3.12

Actions

Copy link

#15

Updated by Vincent MEMBRÉ almost 5 years ago

Target version changed from 4.3.12 to 4.3.13

Actions

Copy link

#16

Updated by Vincent MEMBRÉ almost 5 years ago

Target version changed from 4.3.13 to 4.3.14

Actions

Copy link

#17

Updated by François ARMAND almost 5 years ago

Translation missing: en.field_tag_list set to Sponsored
Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
User visibility changed from Getting started - demo | first install | level 1 Techniques to Getting started - demo | first install | Technique editor and level 1 Techniques
Priority changed from 0 to 85

Actions

Copy link

#18

Updated by François ARMAND almost 5 years ago

Severity changed from Major - prevents use of part of Rudder | no simple workaround to Minor - inconvenience | misleading | easy workaround
Priority changed from 85 to 69

Actions

Copy link

#19

Updated by Vincent MEMBRÉ almost 5 years ago

Target version changed from 4.3.14 to 587

Actions

Copy link

#20

Updated by Vincent MEMBRÉ almost 5 years ago

Target version changed from 587 to 4.3.14

Actions

Copy link

#21

Updated by Alexis Mousset almost 5 years ago

Target version changed from 4.3.14 to 5.0.13

Probably still there

Actions

Copy link

#22

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 5.0.13 to 5.0.14

Actions

Copy link

#23

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 5.0.14 to 5.0.15

Actions

Copy link

#24

Updated by Benoît PECCATTE over 4 years ago

Effort required set to Medium
Priority changed from 69 to 55

Actions

Copy link

#25

Updated by François ARMAND over 4 years ago

Effort required changed from Medium to Small
Priority changed from 55 to 82

We have an easy generic solution:

- rename "total memory" as "os memory"
- add a "total physical memory" as sum of all slots.

We must not change API keys, so we likely need to had one new (os memory), make it the default, and change current total physical to optionnal.

Actions

Copy link

#26

Updated by Alexis Mousset over 4 years ago

Category changed from Agent to Web - Nodes & inventories

Actions

Copy link

#27

Updated by Benoît PECCATTE over 4 years ago

For people who want to test we xen it is on ubuntu-18-04-64.labo.normation.com that is on orchestrateur-4.labo.normation.com

Actions

Copy link

#28

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 5.0.15 to 5.0.16

Actions

Copy link

#29

Updated by Alexis Mousset about 4 years ago

Target version changed from 5.0.16 to 5.0.17

Actions

Copy link

#30

Updated by Vincent MEMBRÉ about 4 years ago

Target version changed from 5.0.17 to 5.0.18

Actions

Copy link

#31

Updated by François ARMAND almost 4 years ago

User visibility changed from Getting started - demo | first install | Technique editor and level 1 Techniques to Operational - other Techniques | Rudder settings | Plugins
Effort required deleted (~~Small~~)
Priority changed from 82 to 55