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.
Description of problem:
Specify the number of cpu cores in qemu-kvm command line, but in guest cpu cores=1 or 0.
Version-Release number of selected component (if applicable):
cpu model of host is SandyBridge
# uname -r
3.7.0-0.30.el7.x86_64
# rpm -qa | grep qemu-kvm
qemu-kvm-1.3.0-3.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Boot gutest using the command line:
/usr/libexec/qemu-kvm -M pc-1.3 -cpu Nehalem -enable-kvm -m 2048 -smp 16,cores=4,threads=2,sockets=2 -name rhel7 -uuid 6afa5f93-2d4f-420f-81c6-e5fdddbd1c83 -drive file=rhel7-64-gui.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,serial=40c061dd-5d60-4fc5-865f-55db700407f0,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:42:0a:00,bus=pci.0,addr=0x3 -vnc :1 -monitor stdio
2.In the guest, cat /proc/cpuinfo
Actual results:
# cat /proc/cpuinfo | grep "physical id" | wc -l
16
# cat /proc/cpuinfo | grep "physical id" | sort | uniq
physical id : 0
physical id : 1
# cat /proc/cpuinfo | grep "cpu cores" | uniq
cpu cores : 1
cpu cores : 0
cpu cores : 1
cpu cores : 0
# cat /proc/cpuinfo | grep "siblings" | uniq
siblings : 1
Expected results:
cpu cores should be 4 and siblings should be 8.
Additional info:
Set the guest cpu model to SandyBridge or Westmere, the result is OK.
Set the guest cpu model to Penryn or Conroe, the result is fail same as Nehalem.