-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
3.0.10
-
None
-
2
-
Severity 2 - Major
-
Issue Summary
Discovery scan does not retrieve the right number of VCPUs vs CPUs
Steps to Reproduce
- enable Windows patterns (WMI or PS)
- set Discovery to scan Windows hosts where CPUs number is different than VCPUs number
- observe that the commands executed for both patterns:
WMIQuery
Windows_CPUs.pat
SELECT * FROM Win32_Processorand
PowerShellExecute
Windows_CPUs_PS.pat
Get-WmiObject Win32_Processor
Are always retrieving the same number of CPUs and VCPUs even if number of VCPUs is different as we can see in Windows device management system info.
This goes for several different Win versions.
Expected Results
The command executed should retrieve the correct number of VCPUs
Actual Results
The command executed do not retrieve the correct number of VCPUs
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- was cloned as
-
JSDSERVER-11831 Discovery scan does not retrieve the right number of VCPUs vs CPUs
-
- Closed
-
- depends on
-
JSMDC-18612 You do not have permission to view this issue
[JSDSERVER-10966] Discovery scan does not retrieve the right number of VCPUs vs CPUs
Remote Link | New: This issue links to "JSMDC-18612 (JIRA Server (Bulldog))" [ 821875 ] |
Link |
New:
This issue was cloned as |
Resolution | New: Not a bug [ 12 ] | |
Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
Status | Original: Gathering Impact [ 12072 ] | New: In Progress [ 3 ] |
Assignee | New: vgedzhev [ 8a797fe2b442 ] |
Support reference count | Original: 1 | New: 2 |
Support reference count | New: 1 |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |