Hide Forgot
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)