Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Error msg should be more user friendly and precise when attaching memory device without guest numa configured.
Version-Release number of selected component (if applicable):
# rpm -q libvirt
libvirt-8.9.0-2.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Start a guest vm without maxMemory and guest numa configured.
# virsh start vm1
Domain 'vm1' started
2.Prepare a memory device xml like below:
<memory model='dimm'>
<source>
<pagesize unit='KiB'>1048576</pagesize>
<nodemask>0-1</nodemask>
</source>
<target>
<size unit='KiB'>1048576</size>
<node>0</node>
</target>
</memory>
3.Attach the memory device with xml from step2.
# virsh attach-device vm1 dimm1G.xml
error: Failed to attach device from dimm1G.xml
error: can't add memory backend for guest node '0' as the guest has only '0' NUMA nodes configured
Actual results:
Unfriendly error msg prompts:
error: can't add memory backend for guest node '0' as the guest has only '0' NUMA nodes configured
Expected results:
The error msg should be more friendly and precise to describe the issue
Additional info:
if define maxMemory and only 1 guest numa cell '0' like below:
<maxMemory slots='16' unit='KiB'>15242880</maxMemory>
...
<numa>
<cell id='0' cpus='0-1' memory='2097152' unit='KiB'/>
</numa>
Then the guest vm can be started and attach the memory device.
So the error msg for this issue makes user confused. Since the below scenario also has '0' numa node exists in guest.
Comment 1RHEL Program Management
2023-09-22 17:31:55 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 2RHEL Program Management
2023-09-22 17:32:31 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Description of problem: Error msg should be more user friendly and precise when attaching memory device without guest numa configured. Version-Release number of selected component (if applicable): # rpm -q libvirt libvirt-8.9.0-2.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1.Start a guest vm without maxMemory and guest numa configured. # virsh start vm1 Domain 'vm1' started 2.Prepare a memory device xml like below: <memory model='dimm'> <source> <pagesize unit='KiB'>1048576</pagesize> <nodemask>0-1</nodemask> </source> <target> <size unit='KiB'>1048576</size> <node>0</node> </target> </memory> 3.Attach the memory device with xml from step2. # virsh attach-device vm1 dimm1G.xml error: Failed to attach device from dimm1G.xml error: can't add memory backend for guest node '0' as the guest has only '0' NUMA nodes configured Actual results: Unfriendly error msg prompts: error: can't add memory backend for guest node '0' as the guest has only '0' NUMA nodes configured Expected results: The error msg should be more friendly and precise to describe the issue Additional info: if define maxMemory and only 1 guest numa cell '0' like below: <maxMemory slots='16' unit='KiB'>15242880</maxMemory> ... <numa> <cell id='0' cpus='0-1' memory='2097152' unit='KiB'/> </numa> Then the guest vm can be started and attach the memory device. So the error msg for this issue makes user confused. Since the below scenario also has '0' numa node exists in guest.