From: Xiangyu Chen <xiangyu.chen@eng.windriver.com>
To: meta-virtualization@lists.yoctoproject.org
Subject: [meta-virtualization][PATCH] libvirt: fix missing dmidecode on arm/aarch64 platform
Date: Thu, 30 Nov 2023 16:53:32 +0800 [thread overview]
Message-ID: <20231130085332.1352490-1-xiangyu.chen@eng.windriver.com> (raw)
From: Xiangyu Chen <xiangyu.chen@windriver.com>
When using libvirtd on aarch64 platform, after system bootup, the log of libvirtd
contains an error as below:
libvirtd[417]: internal error: Child process (/usr/sbin/dmidecode -q -t 0,1,2,3,4,11,17)
unexpected exit status 127:
libvirt: error : cannot execute binary /usr/sbin/dmidecode: No such file or directory
After checking the libvirt source code, the arm/aarch64 also try to call dmidecode to get
the system information[1], so add the dmidecode as depends under arm and aarch64 platform.
Ref:
[1] https://github.com/libvirt/libvirt/blob/master/src/util/virsysinfo.c#L429
Signed-off-by: Xiangyu Chen <xiangyu.chen@windriver.com>
---
recipes-extended/libvirt/libvirt_9.6.0.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/recipes-extended/libvirt/libvirt_9.6.0.bb b/recipes-extended/libvirt/libvirt_9.6.0.bb
index c5d0d2cd..b63087e8 100644
--- a/recipes-extended/libvirt/libvirt_9.6.0.bb
+++ b/recipes-extended/libvirt/libvirt_9.6.0.bb
@@ -18,6 +18,8 @@ RDEPENDS:${PN} = "gettext-runtime"
RDEPENDS:libvirt-libvirtd += "bridge-utils iptables pm-utils dnsmasq netcat-openbsd ebtables"
RDEPENDS:libvirt-libvirtd:append:x86-64 = " dmidecode"
RDEPENDS:libvirt-libvirtd:append:x86 = " dmidecode"
+RDEPENDS:libvirt-libvirtd:append:arm = " dmidecode"
+RDEPENDS:libvirt-libvirtd:append:aarch64 = " dmidecode"
#connman blocks the 53 port and libvirtd can't start its DNS service
RCONFLICTS:${PN}_libvirtd = "connman"
--
2.34.1
next reply other threads:[~2023-11-30 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 8:53 Xiangyu Chen [this message]
2023-12-04 22:19 ` [meta-virtualization][PATCH] libvirt: fix missing dmidecode on arm/aarch64 platform Bruce Ashfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231130085332.1352490-1-xiangyu.chen@eng.windriver.com \
--to=xiangyu.chen@eng.windriver.com \
--cc=meta-virtualization@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).