Comment 3 for bug 1836994

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.