cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daan Hoogland (JIRA)" <>
Subject [jira] [Closed] (CLOUDSTACK-5071) Allow topology definition (socket/core) in the service offering (KVM)
Date Wed, 08 Feb 2017 09:23:58 GMT


Daan Hoogland closed CLOUDSTACK-5071.
    Resolution: Won't Fix

> Allow topology definition (socket/core) in the service offering (KVM)
> ---------------------------------------------------------------------
>                 Key: CLOUDSTACK-5071
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.2.0
>            Reporter: Arnaud G
>            Priority: Critical
> Today if you create a VM for KVM you can only export vcpu and not core, The complete
topology should be provided in order to really support Windows VM on KVM. 
> Windows VM for licensing issue can only see a limited number of socket (for instance
2 for Windows 7/8 or 4 for Windows server standard 2008/2012). This means that with the current
implementation it is impossible to make the VM really benefit from the underlying hardware
and limit the capability to use Windows VM on Cloudstack + KVM.
> Currently CPU are exported as: 
> <vcpu>8</vcpu>
> and it should rather be done like this:
> <vcpu>1</vcpu> <cpu>
> <topology sockets='1' cores='8' threads='1'/>
> </cpu>
> The setup of this kind of configuration should be part of the service offering. (it will
involve a GUI modification)
> This improvement request is linked to CLOUDSTACK-904. This JIRA should be close if this
improvement is accepted.

This message was sent by Atlassian JIRA

View raw message