cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arnaud G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-904) CloudStack export the CPU as a socket not core
Date Mon, 11 Nov 2013 16:35:18 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819096#comment-13819096
] 

Arnaud G commented on CLOUDSTACK-904:
-------------------------------------

Hello,

I created CLOUDSTACK-5071 to follow up on this issue, however it seems that it was quite unnoticed
despite the fact that this bug is critical for KVM.



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

Mime
View raw message