[erikbocks]

Description

The KVMHostInfo class used formatted strings for its logs and displayed an ERROR level log for a normal operation. This PR standardizes the class logging to use parametrized logging, and also fixes some typos in variable names

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)
• Build/CI
• Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

• Major
• Minor

Screenshots (if appropriate):

How Has This Been Tested?

The code was built with Maven.

[codecov]

Codecov Report

❌ Patch coverage is 70.37037% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 20.77%. Comparing base (2f34b0c) to head (b3655a0).

Files with missing lines	Patch %	Lines
...org/apache/cloudstack/utils/linux/KVMHostInfo.java	70.37%	8 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #14226      +/-   ##
============================================
- Coverage     20.77%   20.77%   -0.01%     
  Complexity    20847    20847              
============================================
  Files          6053     6053              
  Lines        548222   548230       +8     
  Branches      73236    73236              
============================================
- Hits         113896   113887       -9     
- Misses       420984   421002      +18     
+ Partials      13342    13341       -1     

Flag	Coverage Δ
uitests	3.86% <ø> (ø)
unittests	22.20% <70.37%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Warning

Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.

Copilot review overview

Review effort: Lite
Findings: 2 · 1

Open (3)

• The failure is currently split into two separate log events (a debug message and a separate… · New
• LOGGER.trace(e) is likely calling the trace(Object message) overload (Log4j2 supports… · New
• This line appears to have an extra leading space compared to surrounding indentation, which can… · New

What changed in this PR

This PR standardizes KVMHostInfo logging to use parameterized logging (instead of String.format) and fixes a couple of typos/inconsistent names.

Changes:

• Replace formatted-string logs with parameterized logs across CPU/memory discovery paths
• Fix typos/inconsistent naming (cpabilities → capabilities, cpusockets → cpuSockets)
• Add helper methods to centralize CPU-speed command logging and failure logging

File	Description
plugins/​hypervisors/​kvm/​src/​main/​java/​org/​apache/​cloudstack/​utils/​linux/​KVMHostInfo.java	Refactors logging to parameterized form, fixes naming/typos, and adds helper logging methods for CPU-speed retrieval

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Warning

Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.

Copilot review overview

Review effort: Lite
Findings: 3

Open (3)

• LOGGER.trace(e); logs the exception object as the message (typically only toString()), and does… · New
• LOGGER.trace(e) is likely calling the trace(Object message) overload (Log4j2 supports…
• The failure is currently split into two separate log events (a debug message and a separate…

Resolved since last review (1)

• This line appears to have an extra leading space compared to surrounding indentation, which can…

[github-actions]

This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch.