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.
This bug also occur in rhel7.
Package version:
libvirt-1.1.1-29.el7.x86_64
qemu-kvm-rhev-1.5.3-60.el7ev.x86_64
kernel-3.10.0-123.el7.x86_64
+++ This bug was initially created as a clone of Bug #1098101 +++
Description:
Disable one host cpu, then enabled it back. Then it can't be shown in the output of the guest vcpuinfo.
Even restart the guest and libvirtd, the "CPU Affinity" info is still not correct.
Waiting for half day, the "CPU Affinity" info is still not correct.
The only resolved method is to reboot the host, then the "CPU Affinity" info will be correctly.
How reproducible:
100%
Version:
libvirt-0.10.2-35.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.425.el6.x86_64
kernel-2.6.32-463.el6.x86_64
Steps:
１． prepare one running guest, and check the vcpuinfo of this guest.
# virsh start rhel6.5
Domain rhel6.5 started
# virsh vcpuinfo rhel6.5
VCPU: 0
CPU: 0
State: running
CPU time: 4.9s
CPU Affinity: yyyy
2. check the online cpus of this host.
# cat /sys/devices/system/cpu/online
0-3
3. disable one cpu of the host.
# echo 0 > /sys/devices/system/cpu/cpu2/online
# cat /sys/devices/system/cpu/cpu2/online
0
# cat /sys/devices/system/cpu/online
0-1,3
4. check the vcpuinfo of the guest.
# virsh vcpuinfo rhel6.5
VCPU: 0
CPU: 0
State: running
CPU time: 33.7s
CPU Affinity: yy-y
5. enable the 2nd cpu on host.
# echo 1 > /sys/devices/system/cpu/cpu2/online
# cat /sys/devices/system/cpu/cpu2/online
1
# cat /sys/devices/system/cpu/online
0-3
6. check the vcpuinfo of the guest again
# virsh vcpuinfo rhel6.5
VCPU: 0
CPU: 1
State: running
CPU time: 32.8s
CPU Affinity: yy-y
7. destroy and start the guest, then, check vcpuinfo again.
# virsh destroy rhel6.5
Domain rhel6.5 destroyed
# virsh start rhel6.5
Domain rhel6.5 started
# virsh vcpuinfo rhel6.5
VCPU: 0
CPU: 0
State: running
CPU time: 2.5s
CPU Affinity: yy-y
8. restart libvirtd and recheck.
# service libvirtd restart
Stopping libvirtd daemon: [ OK ]
Starting libvirtd daemon: [ OK ]
# virsh destroy rhel6.5
Domain rhel6.5 destroyed
# virsh start rhel6.5
Domain rhel6.5 started
# virsh vcpuinfo rhel6.5
VCPU: 0
CPU: 0
State: running
CPU time: 0.5s
CPU Affinity: yy-y
Actual results:
As step 6, 7 and 8
Expected results:
The CPU Affinity should be show the active pinned cpu after the cpu is enabled.