Bug 468947 - VirtualBox VM memoryused not reported
Summary: VirtualBox VM memoryused not reported
Status: RESOLVED DUPLICATE of bug 444323
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (show other bugs)
Version: 5.27.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-25 12:38 UTC by Méven Car
Modified: 2024-02-19 14:49 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Méven Car 2023-04-25 12:38:51 UTC 
SUMMARY

STEPS TO REPRODUCE
1. Run a VM in Virtualbox (in my case Neon)
2. Look in plasma-system-monitor in the host, the process view for the VirtualBoxVM process

OBSERVED RESULT
Memory column empty for the VM process.

EXPECTED RESULT
some memory usage is reported for the VM


SOFTWARE/OS VERSIONS
Operating System: Kubuntu 23.04
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 5.19.0-40-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3800X 8-Core Processor
Memory: 31.3 Gio of RAM
Comment 1 Riccardo Robecchi 2023-05-04 10:29:11 UTC 
I can confirm the bug.
Comment 2 popov895 2024-02-18 08:19:25 UTC 
Duplicate of BUG 444323?
Comment 3 Arjen Hiemstra 2024-02-19 14:49:24 UTC 
To an extent. In this case, the file is most likely not readable because VirtualBox protects it, rather than it being owned by a different user. In any case, for both the solution would be the same (some way of elevating to read the process data).

*** This bug has been marked as a duplicate of bug 444323 ***