Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F362910701 for ; Wed, 6 Nov 2013 20:18:18 +0000 (UTC) Received: (qmail 73559 invoked by uid 500); 6 Nov 2013 20:18:18 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 73529 invoked by uid 500); 6 Nov 2013 20:18:18 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 73521 invoked by uid 500); 6 Nov 2013 20:18:18 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 73518 invoked by uid 99); 6 Nov 2013 20:18:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Nov 2013 20:18:18 +0000 Date: Wed, 6 Nov 2013 20:18:18 +0000 (UTC) From: =?utf-8?Q?Ren=C3=A9_Diepstraten_=28JIRA=29?= To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-904) CloudStack export the CPU as a socket not core MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-904?page=3Dcom.atlas= sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D= 13815245#comment-13815245 ]=20 Ren=C3=A9 Diepstraten commented on CLOUDSTACK-904: --------------------------------------------- That seems good to me. In any case, this should be solved. It requires some discussion about how it should be implemented and, if it should be possible to both configure sockets and cores, may require changes in the gui as well. Therefore a feature request seems a right choice to me. [ https://issues.apache.org/jira/browse/CLOUDSTACK-904?page=3Dcom.atlassian.j= ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D138150= 60#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? default.) 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 !! the CPUs as sockets not cores and this version of windows support only up to 4 cores. as following : you cannot have the required service offer. -- This message was sent by Atlassian JIRA (v6.1#6144) > 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 defa= ult.)=20 > 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 worki= ng on a 4 cores offer. when I upgraded the service offer to 8 cores and che= cked 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 t= he 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 : > 8 > and it should be exported as following: > 1 > > > otherwise in such systems where you are limited with the sockets number y= ou cannot have the required service offer. -- This message was sent by Atlassian JIRA (v6.1#6144)