Bug 2359736 - libvirtd uses the wrong path for numad and fails to start domains
Summary: libvirtd uses the wrong path for numad and fails to start domains
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 42
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-15 12:25 UTC by Mathieu
Modified: 2025-05-03 02:09 UTC (History)
9 users (show)

Fixed In Version: libvirt-11.0.0-2.fc42
Clone Of:
Environment:
Last Closed: 2025-05-03 02:09:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mathieu 2025-04-15 12:25:30 UTC
After upgrading to F42, if I try to start a domain, I get the following message:

error: operation failed: Failed to query numad for the advisory nodeset

After enabling the logs, I find the error:
2025-04-15 11:41:53.285+0000: 2626: error : virCommandWait:2770 : internal error: Child process (/sbin/numad -w 24:32768) unexpected exit status 127: libvirt:  error : cannot execute binary /sbin/numad: No such file or directory

This is expected: /sbin/numad doesn't exist, it's really /usr/bin/numad...

# strings /usr/lib64/libvirt.so.0 | fgrep /sbin/numad
/sbin/numad

# rpm -qf /usr/lib64/libvirt.so.0
libvirt-libs-11.0.0-1.fc42.x86_64

# rpm -ql numad | fgrep bin/
/usr/bin/numad

# rpm -qf /usr/bin/numad
numad-0.5-46.20150602git.fc42.x86_64

Reproducible: Always

Comment 1 Daniel Berrangé 2025-04-15 15:17:05 UTC
> This is expected: /sbin/numad doesn't exist, it's really /usr/bin/numad...

Can you show me 'ls -lad /sbin /usr/sbin' ?  In a Fedora 42 container /  Fedora 42 build environment both these directories are symlinks that end up pointing to /usr/bin.

This means that when libvirt is build, all of '/sbin/numad', '/usr/sbin/numad' and '/usr/bin/numad' are valid paths, and meson picks the first which happens to be a symlink rather than the canonical location.

This would be fine if the deployed system also had /sbin symlinking to /usr/bin.

Comment 2 Mathieu 2025-04-17 00:06:21 UTC
Yes that's indeed the issue, just realized that myself, it's failed migration from /usr/sbin to .usr/bin.

There's thread here which documents the same problematic packages: https://discussion.fedoraproject.org/t/f42-change-proposal-unify-usr-bin-and-usr-sbin-system-wide/99853/42

$ find /usr/sbin/ -type f | xargs rpm -qf | sort -u
dnsmasq-2.90-4.fc42.x86_64
iscsi-initiator-utils-6.2.1.10-0.gitd0f04ae.fc41.1.x86_64
iscsi-initiator-utils-iscsiuio-6.2.1.10-0.gitd0f04ae.fc41.1.x86_64

I am closing this bug as the problem is clearly not with libvirtd...

Thanks for getting back to me.

Comment 3 Daniel Berrangé 2025-04-17 09:28:42 UTC
Re-opening as this is actually a flaw in libvirt. We should have done a better  job at picking the numad path in our meson.build file to avoid this problem

Comment 4 Fedora Update System 2025-04-29 16:00:04 UTC
FEDORA-2025-517115afd6 (libvirt-11.0.0-2.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-517115afd6

Comment 5 Fedora Update System 2025-04-30 01:29:16 UTC
FEDORA-2025-517115afd6 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-517115afd6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-517115afd6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2025-05-03 02:09:13 UTC
FEDORA-2025-517115afd6 (libvirt-11.0.0-2.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.