Bug 2224016

Summary: virtqemud: internal error: Missing or invalid CPU address size in /proc/cpuinfo
Product: Red Hat Enterprise Linux 9 Reporter: Boris Fiuczynski (IBM) <bfiuczyn>
Component: libvirtAssignee: Boris Fiuczynski (IBM) <bfiuczyn>
libvirt sub component: General QA Contact: smitterl
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: clegoate, hhan, jdenemar, lcong, lmen, smitterl, thuth, virt-maint
Version: 9.3Keywords: Triaged
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 9.3   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: libvirt-9.5.0-3.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-07 08:31:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Boris Fiuczynski (IBM) 2023-07-19 14:59:30 UTC
Description of problem:
virtqemud reports on startup an internal error.

Version-Release number of selected component (if applicable):
libvirt 9.5.0

How reproducible:
every time

Steps to Reproduce:
1. run an API call against the virtqemud, e.g. 'virsh list'
2. check journalctl

Actual results:
Jul 17 12:18:35 m83lp64 virtqemud[42738]: libvirt version: 9.6.0, package: 4167.kvm.20230707.d369a1d5ae (Unknown, 2023-07-07-09:43:21, )
Jul 17 12:18:35 m83lp64 virtqemud[42738]: hostname: m83lp64
Jul 17 12:18:35 m83lp64 virtqemud[42738]: internal error: Missing or invalid CPU address size in /proc/cpuinfo

Expected results:
no internal error should be reported

Additional info:

Comment 1 Boris Fiuczynski (IBM) 2023-07-19 15:01:19 UTC
Fix is available upstream.

https://gitlab.com/libvirt/libvirt/-/commit/8417c1394cd4deccee07235d4f7b2c54b774b08d

Comment 2 Boris Fiuczynski (IBM) 2023-07-21 12:29:43 UTC
Backported: https://gitlab.com/redhat/rhel/src/libvirt/-/merge_requests/118

Comment 3 smitterl 2023-07-24 12:59:52 UTC
Pre-verified with libvirt-9.5.0-3.el9.s390x

Comment 6 liang cong 2023-08-16 02:56:01 UTC
Verified on build libvirt-9.5.0-5.el9.s390x

Test steps:
1. Grep related error info in journalctl:
# journalctl --no-pager | grep virtqemud | grep -F 'cpuinfo'

2. Check journalctl for related virtqemud log, no bug related error message found:
Aug 15 05:11:21 z15l43.s390g.lab.eng.rdu2.redhat.com virtqemud[143671]: 2023-08-15 09:11:21.379+0000: 143671: info : libvirt version: 9.5.0, package: 5.el9 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2023-08-02-18:28:48, )
Aug 15 05:11:21 z15l43.s390g.lab.eng.rdu2.redhat.com virtqemud[143671]: 2023-08-15 09:11:21.379+0000: 143671: info : hostname: z15l43.s390g.lab.eng.rdu2.redhat.com
Aug 15 05:11:21 z15l43.s390g.lab.eng.rdu2.redhat.com virtqemud[143671]: 2023-08-15 09:11:21.379+0000: 143671: debug : virLogParseOutputs:1641 : outputs=1:file:/var/log/libvirt/libvirtd.log 3:journald

Comment 7 liang cong 2023-08-16 02:57:06 UTC
Mark it verified per comment 3 and comment 5

Comment 9 errata-xmlrpc 2023-11-07 08:31:41 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: libvirt security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:6409