cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3501) Cannot create instances on XenServer with multiple cores per socket
Date Fri, 26 Jul 2013 09:37:49 GMT

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

ASF subversion and git services commented on CLOUDSTACK-3501:
-------------------------------------------------------------

Commit b4667290080ac7758c0fef934ce28bbae17dbee2 in branch refs/heads/4.2 from [~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b466729 ]

CLOUDSTACK-3501. Cannot create instances on XenServer with multiple cores in a socket. If
details has information on cores per socket, create an instance accordingly. The vm record
is populated with information on how many cores should be allowed in a socket.

                
> Cannot create instances on XenServer with multiple cores per socket
> -------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3501
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3501
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: Devdeep Singh
>            Assignee: Devdeep Singh
>            Priority: Critical
>
> It is possible to create vms on a hypervisor with multiple cores per socket. However,
right now we cannot do that with cloudstack. For example, on XenServer if you choose a service
offering with 4 cpus, an instance get deployed with 4 vcpus. Cloudstack should let a user
deploy an instance with multiple cores in a socket. In this case it could be 4 cores in 1
socket.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message