Landscape SAAS is reporting an odd RAM amount for VMs on Hyper-V

Bug #1836994 reported by Jose Delarosa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client
Confirmed
Undecided
Unassigned

Bug Description

Landscape SAAS is reporting an odd RAM amount for certain VMs on Hyper-V.

For example,
Memory Information

Size: 803 TiB RAM

cat /proc/meminfo
MemTotal: 49427596 kB
MemFree: 45278020 kB
MemAvailable: 48166560 kB
Buffers: 22908 kB
Cached: 3186272 kB
SwapCached: 0 kB

Revision history for this message
Jose Delarosa (jdelaros1) wrote :

Screenshot attached

summary: - Landscape SAAS is reporting an odd RAM amount VMs on Hyper-V
+ Landscape SAAS is reporting an odd RAM amount for VMs on Hyper-V
Revision history for this message
Simon Poirier (simpoir) wrote :

While I'm not familiar with Hyper-V, but allow me to guess

Landscape use lshw to create the hardware inventory. This probes hardware directly to know the ram available and does not depend on drivers and software support, unlike the proc filesystem.

Since it was specified this issue affects only some VMs, I suspect it's particular to their configuration. Hyper-V has a "dynamic memory" configuration to have VMs shrink and grow on demand. If I had to guess, those VMs have that setting on, thus having a non-fixed memory size. Hyper-V probably exposes that "hardware" as the maximum addressable size it supports (i.e. the absurdly large 803TiB).

If that's the case, there is little we can do in landscape to fix the hardware report since those are the values the hypervisor sends it. Graphs don't use that data and look correct.

information type: Proprietary → Public
description: updated
description: updated
description: updated
Simon Poirier (simpoir)
Changed in landscape:
status: New → Confirmed
Simon Poirier (simpoir)
affects: landscape → landscape-client
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.