Back to bug 2185039
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2023-04-06 15:10:42 UTC | Pool ID | sst_virtualization_rhel_9 | |
| Red Hat One Jira (issues.redhat.com) | 2023-04-06 15:13:06 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-154190 | |
| yalzhang | 2023-04-06 17:26:15 UTC | QA Contact | virt-bugs | lhuang |
| Michal Privoznik | 2023-04-12 07:27:54 UTC | Doc Type | If docs needed, set a value | Bug Fix |
| Doc Text | When starting a misconfigured guest (such that the emulator thread is pinned onto NUMA node(s) distinct to NUMA node(s) of guest memory) AND using allocation threads (/domain/memoryBacking/allocation/@threads), the guest refuses to start with an error. This is because those allocation threads have their affinity set to those NUMA nodes of the guest memory, but are created from the context of the emulator thread (which itself is already restricted to given NUMA nodes). These patches prune inaccessible NUMA nodes by computing an intersection between two sets of NUMA nodes and setting affinity to only the intersecting ones. This allows guest to start again. | |||
| Status | NEW | POST | ||
| Jiri Denemark | 2023-04-14 11:21:40 UTC | Fixed In Version | libvirt-9.0.0-10.1.el9_2 | |
| Status | POST | MODIFIED | ||
| errata-xmlrpc | 2023-04-17 13:57:10 UTC | Status | MODIFIED | ON_QA |
| Luyao Huang | 2023-04-18 08:09:34 UTC | Status | ON_QA | VERIFIED |
| Luyao Huang | 2023-04-18 09:27:29 UTC | Keywords | AutomationBackLog | |
| Dan Zheng | 2023-04-20 04:08:03 UTC | CC | dzheng | |
| errata-xmlrpc | 2023-05-09 00:41:51 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-05-09 11:04:43 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2023-05-09 11:04:43 UTC | |||
| errata-xmlrpc | 2023-05-09 11:04:49 UTC | Link ID | Red Hat Product Errata RHBA-2023:2632 | |
| Dan Zheng | 2023-05-22 13:02:45 UTC | Link ID | Red Hat Issue Tracker LIBVIRTAT-14221 | |
| Dan Zheng | 2023-07-26 08:40:06 UTC | Keywords | AutomationBackLog |
Back to bug 2185039