[
https://issues.apache.org/jira/browse/CLOUDSTACK-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815060#comment-13815060
]
Arnaud G commented on CLOUDSTACK-904:
-------------------------------------
Seems that the problem was closed for Xen (see CLOUDSTACK-3501) but for KVM
there is no progress.
This feature is critical in order to have Windows server with more than 4
cores. The lack of export of a correct topology is a blocking point. It is
currently not possible to create "big" (more than for 4 cores/socket) Windows
Server VM on Cloudstack+KVM....
Should we close this and reopen a feature request?
> CloudStack export the CPU as a socket not core
> ----------------------------------------------
>
> Key: CLOUDSTACK-904
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-904
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
> Affects Versions: pre-4.0.0, 4.0.0
> Reporter: Ahmad Saif
>
> I've a VM that's running (Windows 2008 Standard R2 64bit) which was working
> on a 4 cores offer. when I upgraded the service offer to 8 cores and checked
> the VM I noticed that it still have only 4 cores !!
> I dig a little bit on the windows machine itself, and found that it see the
> CPUs as sockets not cores and this version of windows support only up to 4
> cores.
> when I checked the vm XML file on the host I saw that the CPU is exported as
> following :
> <vcpu>8</vcpu>
> and it should be exported as following:
> <vcpu>1</vcpu> <cpu>
> <topology sockets='1' cores='8' threads='1'/>
> </cpu>
> otherwise in such systems where you are limited with the sockets number you
> cannot have the required service offer.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
