Bug #3459
OpenNebula generates template with 12 sockets instead of 12 cores
Status: | Closed | Start date: | 12/16/2014 | |
---|---|---|---|---|
Priority: | High | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | - | |||
Target version: | - | |||
Resolution: | duplicate | Pull request: | ||
Affected Versions: | OpenNebula 4.10 |
Description
When instantiating instances with more then 1 vcpu, qemu-kvm runs with...
-smp X,sockets=X,cores=1,threads=1
X being the vcpu assigned.
It seems to be fine in Linux guest as it can still uses more than 1 vcpu, however in Windows guest it only use 2 cores/sockets/processors. I created a VM with 16 vcpu with 16 real cpu on a dual socket server, it runs with...
-smp 16,sockets=16,cores=1,threads=1
And Windows guest can only see 2 processors despite that the license is permitted to have more than 2 sockets.
Also, I'm concerning if that is NUMA-aware.
Related issues
History
#1 Updated by Ruben S. Montero over 6 years ago
- Status changed from Pending to Closed
- Resolution set to duplicate
#2 Updated by Ruben S. Montero over 6 years ago
- Duplicates Backlog #796: Include cpu tune & topology parameters for qemu/libvirt drivers added
#3 Updated by Ruben S. Montero over 6 years ago
- Related to Backlog #2869: Add the ability to configure the CPU model exposed to KVM virtual machines. added