shaerul opened a new issue, #8453:
URL: https://github.com/apache/cloudstack/issues/8453
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
CloudStack Instance Metrics (Memory)
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.18.1.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Windows Server 2022 Instance on QEMU/KVM Host
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
QEMU/KVM Installed on Ubuntu 20.04 LTS Host
##### SUMMARY
<!-- Explain the problem/feature briefly -->
I've set up a Windows Server 2022 on a QEMU/KVM host running Ubuntu 20.04
LTS. Since the initial setup, CloudStack's Instance Metrics consistently
display 100% memory utilization, contrary to the Windows Task Manager, which
consistently shows only 9%. Despite installing "virtio-win-guest-tools" from
"virtio-win-0.1.240.iso" on the Windows Server 2022 VM, the issue persists.
Interestingly, instances created from Ubuntu, CentOS, and Alpine Linux
exhibit accurate metrics, reflecting proper allocation and usage.
Could you provide assistance in resolving this bug or problem?
<img width="955" alt="windows-mem-bug"
src="https://github.com/apache/cloudstack/assets/5109336/92129c9e-245d-4bcd-acce-3984beef060b";>
<img width="890" alt="windows-mem-bug-1"
src="https://github.com/apache/cloudstack/assets/5109336/5a693069-e4c2-4e14-bf73-6135ec26a5e3";>
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
