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.

I'd expect -smp 1,cores=2 to give me a guest with a dual core socket == 2 logical CPUs exposed to the guest. Instead I see just 1 logical CPU in /proc/cpuinfo: a socket claiming 2 cores but only 1 core is listed.

Ideally I'd think that if any topology info is specified, old style -smp X is ignored, and the logical CPU number is just calculated, defaulting unspecified topology values to 1. Or have old style -smp X just be the old way of specifying sockets=X, and if sockets= is specified, -smp X is ignored.

And even if nothing is changed the docs should mention these semantics (which isn't really relevant for RHEL but still worth mentioning).

(see https://bugzilla.redhat.com/show_bug.cgi?id=708892#c2 for some more background)

(In reply to comment #0)
> I'd expect -smp 1,cores=2 to give me a guest with a dual core socket == 2
> logical CPUs exposed to the guest. Instead I see just 1 logical CPU in
> /proc/cpuinfo: a socket claiming 2 cores but only 1 core is listed.

I think the current syntax requires -smp 2, cores=2.
Agree it is not the easiest. I doubt we'll be able to change it now.
If the above does not work, please reopen the bug

> 
> Ideally I'd think that if any topology info is specified, old style -smp X is
> ignored, and the logical CPU number is just calculated, defaulting unspecified
> topology values to 1. Or have old style -smp X just be the old way of
> specifying sockets=X, and if sockets= is specified, -smp X is ignored.
> 
> And even if nothing is changed the docs should mention these semantics (which
> isn't really relevant for RHEL but still worth mentioning).
> 
> (see https://bugzilla.redhat.com/show_bug.cgi?id=708892#c2 for some more
> background)