Bug 2103620
| Summary: | isolate_thread VM configured with correct topology that must fit the host can't start | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Polina <pagranat> | ||||
| Component: | BLL.Virt | Assignee: | Liran Rotenberg <lrotenbe> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Polina <pagranat> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.5.1 | CC: | ahadas, bugs, dfodor | ||||
| Target Milestone: | ovirt-4.5.2 | Flags: | pm-rhel:
ovirt-4.5?
|
||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | ovirt-engine-4.5.2 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-08-30 08:47:42 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
verified on ovirt-engine-4.5.1.3-0.36.el8ev.noarch by running automation test rhevmtests.compute.sla.vms_dedicated_policy.isolated_threads_policy.TestMigrationIsolatedVMBasic This bugzilla is included in oVirt 4.5.2 release, published on August 10th 2022. Since the problem described in this bug report should be resolved in oVirt 4.5.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |
Created attachment 1894455 [details] logs Description of problem:happens to isolate_thread VMs with (sockets number) = (host socket number) and (cores number) = (host sockets -1) Version-Release number of selected component (if applicable): ovirt-engine-4.5.1.2-0.11.el8ev.noarch How reproducible: 100% Steps to Reproduce: 1. on host with topology like CPU(s): 32 On-line CPU(s) list: 0-31 Thread(s) per core: 2 Core(s) per socket: 8 Socket(s): 2 NUMA node(s): 2 configure a VM <cpu> <topology> <sockets>2</sockets> <cores>7</cores> <threads>1</threads> </topology> </cpu> <cpu_pinning_policy>isolate_threads</cpu_pinning_policy> 2. run the VM Actual results: Fails to start 2022-07-04 11:29:47,767+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-54) [e1cd692d-2040-4539-b9fb-2cdf452f2c50] EVENT_ID: USER_FAILED_RUN_VM(54), Failed to run VM golden_env_mixed_virtio_0 due to a failed validation: [Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:, The host host_mixed_2 did not satisfy internal filter CpuPinning because it doesn't have enough CPUs for the dedicated CPU policy that the VM is set with.., The host host_mixed_2 did not satisfy internal filter CpuPinning because it doesn't have enough CPUs for the dedicated CPU policy that the VM is set with.., The host host_mixed_2 did not satisfy internal filter CpuPinning because it doesn't have enough CPUs for the dedicated CPU policy that the VM is set with..] (User: admin@internal-authz). Expected results: must start since the topology fits the host from the point of isolated threads policy Additional info: