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.

Bug 1076326

Summary: qemu-kvm does not quit when booting guest w/ 161 vcpus and "-no-kvm"
Product: Red Hat Enterprise Linux 7 Reporter: huiqingding <huding>
Component: qemu-kvmAssignee: Marcelo Tosatti <mtosatti>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 7.0CC: hhuang, huding, juzhang, knoel, mrezanin, mtosatti, rbalakri, virt-maint, xfu
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: qemu-kvm-1.5.3-66.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1126666 (view as bug list) Environment:
Last Closed: 2015-03-05 08:05:12 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 huiqingding 2014-03-14 05:18:53 UTC
Description of problem:
qemu-kvm does not quit when booting guest w/ 161 vcpus and "-no-kvm"

Version-Release number of selected component (if applicable):
qemu-kvm-1.5.3-53.el7.x86_64
kernel-3.10.0-107.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. boot a guest with "-smp 161" and "-no-kvm"
#/usr/libexec/qemu-kvm -no-kvm -smp 161 -m 2G  -monitor stdio -drive file=/home/rhel7.0-64-cp2.raw,if=none,format=raw,werror=stop,rerror=stop,id=drive-ide -device ide-drive,drive=drive-ide,id=test1 -boot c -net none -vnc :10

Actual results:
qemu-kvm doesn't quit, guest hang during boot process with "Failed to acess perfctr msr (MSR c0010004 is 0)"

Expected results:
qemu-kvm should quit.

Additional info:

Comment 6 juzhang 2014-04-28 01:43:45 UTC
Hi Huding,

Can have a try and update the testing result?

Best Regards,
Junyi

Comment 8 Miroslav Rezanina 2014-07-09 12:17:15 UTC
Fix included in qemu-kvm-1.5.3-66.el7

Comment 9 FuXiangChun 2014-08-05 03:17:43 UTC
Reproduced this bug with qemu-kvm-rhev-1.5.3-60.el7ev.x86_64 and "-M pc-q35-rhel7.0.0" or "-M pc-i440fx-rhel7.0.0"

result:
same as comment 0 

verify bug with qemu-kvm-1.5.3-66.el7.x86_64.

result:
1.Number of SMP cpus requested (161), exceeds max cpus supported by machine `pc-q35-rhel7.0.0' (160)

2.Number of SMP cpus requested (161), exceeds max cpus supported by machine `pc-i440fx-rhel7.0.0' (160)

As qemu-kvm-rhev version didn't fix this bug. so QE filed a new bug 1126666.

Comment 13 errata-xmlrpc 2015-03-05 08:05:12 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, 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://rhn.redhat.com/errata/RHSA-2015-0349.html