RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2001390 - "An error occurred, but the cause is unknown" raised when starting VM with non-existed numa node in <numatune>
Summary: "An error occurred, but the cause is unknown" raised when starting VM with no...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.0
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michal Privoznik
QA Contact: Jing Qi
URL:
Whiteboard:
Depends On: 1724866 1806857
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-05 23:47 UTC by John Ferlan
Modified: 2021-09-09 11:00 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1806857
Environment:
Last Closed: 2021-09-09 11:00:23 UTC
Type: Bug
Target Upstream Version: 6.8.0
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-96262 0 None None None 2021-09-05 23:49:31 UTC

Description John Ferlan 2021-09-05 23:47:33 UTC 
+++ This bug was initially created as a clone of Bug #1806857 +++

Description of problem:
"An error occurred, but the cause is unknown" raised when starting VM with non-existed numa node in <numatune>

Version-Release number of selected component (if applicable):
kernel-4.18.0-167.el8.x86_64
qemu-kvm-2.12.0-99.module+el8.2.0+5827+8c39933c.x86_64
libvirt-4.5.0-40.module+el8.2.0+5761+d16d25e7.x86_64

How reproducible:
100%

Steps to Reproduce:
# virsh domstate avocado-vt-vm1
shut off

# virsh numatune avocado-vt-vm1
numa_mode      : strict
numa_nodeset   : 0,41

# virsh start avocado-vt-vm1
error: Failed to start domain avocado-vt-vm1
error: An error occurred, but the cause is unknown

# numactl --hard
available: 4 nodes (0-3)
node 0 cpus: 0 4 8 12 16 20 24 28 32 36 40 44 48 52 56 60
node 0 size: 31714 MB
node 0 free: 29560 MB
node 1 cpus: 1 5 9 13 17 21 25 29 33 37 41 45 49 53 57 61
node 1 size: 32196 MB
node 1 free: 31555 MB
node 2 cpus: 2 6 10 14 18 22 26 30 34 38 42 46 50 54 58 62
node 2 size: 0 MB
node 2 free: 0 MB
node 3 cpus: 3 7 11 15 19 23 27 31 35 39 43 47 51 55 59 63
node 3 size: 0 MB
node 3 free: 0 MB
node distances:
node   0   1   2   3 
  0:  10  16  16  16 
  1:  16  10  16  16 
  2:  16  16  10  16 
  3:  16  16  16  10 

Actual results:
Unreasonable err raised

Expected results:
There should be reasonable err for this scenario

Additional info:
For RHEL-820fast
# rpm -qa libvirt 
libvirt-6.0.0-6.module+el8.2.0+5821+109ee33c.x86_64

# virsh start test82-1 
error: Failed to start domain test82-1
error: unsupported configuration: NUMA node 40 is unavailable

--- Additional comment from RHEL Program Management on 2020-09-30 10:08:04 UTC ---

pm_ack is no longer used for this product. The flag has been reset.

See https://issues.redhat.com/browse/PTT-1821 for additional details or contact lmiksik if you have any questions.

--- Additional comment from Michal Privoznik on 2021-02-15 12:55:19 UTC ---

Merged upstream as:

9e0d4b9240 virnuma: Report error when NUMA -> CPUs translation fails

v6.7.0-86-g9e0d4b9240

--- Additional comment from Jiri Denemark on 2021-03-05 19:16:09 UTC ---

Oops, this is for RHEL. This was addressed in bug 1724866 for RHEL-AV 8.3.0.

--- Additional comment from RHEL Program Management on 2021-07-26 07:30:28 UTC ---

30-day auto-close warning: This bz has been open for an extended time without being approved for a release (has a release+ or zstream+ flag) .  Please consider prioritizing the work appropriately to get it approved for a release, or close the bz.  Otherwise, if it is still open on the “Stale date”, it will close automatically (CLOSED WONTFIX).

--- Additional comment from RHEL Program Management on 2021-08-25 07:27:06 UTC ---

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

--- Additional comment from Michal Privoznik on 2021-08-25 08:01:48 UTC ---

Le sigh. This bug is fixed and we're just waiting for RHEL to pick up rebased version. There's no reason to close this bug!

--- Additional comment from RHEL Program Management on 2021-08-25 08:01:57 UTC ---

This bug was reopened or transitioned from a non-RHEL to RHEL product.  The stale date has been reset to +6 months.
Comment 1 Jiri Denemark 2021-09-09 11:00:23 UTC 
Actually, this bug never existed in any RHEL-9 (beta) build.
Note You need to log in before you can comment on or make changes to this bug.