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.

host:   kernel-3.10.0-54.0.1.el7.x86_64
        qemu-kvm-rhev-1.5.3-35.el7.x86_64
        libvirt-1.1.1-18.el7.x86_64
guest:  kernel-3.10.0-54.0.1.el7.x86_64

Host has 160 cpus

When running 'virsh cpu-stats' cpu 140 output

CPU140:
        cpu_time             0.000000000 seconds
	vcpu_time            0.000000000 seconds
	cpu_time            27.394963770 seconds
	vcpu_time           27.394658147 seconds

The first two outputs are what's strange. This reproduced three times, always for cpu140, but, sigh, now I can't reproduce it...

Unfortunately we weren't able to either reproduce that or find any possibility for it to happen through code inspection (unless somebody is rewriting our memory, of course).  I have to close this for now as there are insufficient data for us to continue.  At least we have a bug to track that it already happened and if this happens again this may be reopened and we are more likely to know where to begin.

Don't hesitate to reopen this bug in case it is reproducible again.