[
https://issues.apache.org/jira/browse/VCL-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607375#comment-16607375
]
ASF subversion and git services commented on VCL-1104:
------------------------------------------------------
Commit de9e192f821807857669f9a7cbe368ee8664e67b in vcl's branch
refs/heads/develop from [~jfthomps]
[ https://git-wip-us.apache.org/repos/asf?p=vcl.git;h=de9e192 ]
VCL-1104 - set cpu topology for libvirt VMs
libvirt.pm: modified generate_domain_xml: added topology to $xml_hashref under
cpu section and logic to set related variables
> set cpu topology for libvirt VMs
> --------------------------------
>
> Key: VCL-1104
> URL: https://issues.apache.org/jira/browse/VCL-1104
> Project: VCL
> Issue Type: Improvement
> Components: vcld (backend)
> Reporter: Josh Thompson
> Priority: Major
> Fix For: 2.5.1
>
>
> Many (all?) versions of Windows only support a maximum of 2 cpu sockets but
> can have many cores per socket. libvirt presents vcpus as single core cpu
> sockets by default. This results in Windows reservations on KVM hosts only
> seeing 2 cpus even if more are assigned. Setting the topology in the cpu
> section of the xml such that there are 2 sockets with the number of cores
> evenly divided between them allows for all assigned cpus to show up (unless
> the VM has an odd number assigned, in which case, it will be one less; the
> frontend should be updated to require 1 core or an even number of cores).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
