Thank you,
Socket doesn't work after I deploy VM with the following command
cmk deploy virtualmachine zoneid=2bc73a3d-4c92-49da-b323-1142a45dca8c
templateid=6802f4cb-2529-48f4-bba9-ff7d82db3ab9
serviceofferingid=b8850bca-88b4-4378-ba70-e87546db58fd name=test-cpu-socket-02
networkids=e28d44cf-9179-4526-81b6-990ef31ec9be detailsp[0].cpu.corespersocket=2
ps: serviceoffering
(localcloud) > list serviceofferings id=b8850bca-88b4-4378-ba70-e87546db58fd
{
"Count": 1,
"serviceoffering": [
{
"cpunumber": 20,
"cpuspeed": 2000,
"created": "2019-08-09T11:11:20+0800",
"defaultuse": false,
"deploymentplanner": "FirstFitPlanner",
"displaytext": "SP01-20C4G",
"domain": "ROOT",
"domainid": "602d9221-e184-11e8-9d95-4ab2a88c1305",
"hosttags": "ha",
"id": "b8850bca-88b4-4378-ba70-e87546db58fd",
"iscustomized": false,
"issystem": false,
"isvolatile": false,
"limitcpuuse": false,
"memory": 4096,
"name": "SP01-20C4G",
"offerha": true,
"provisioningtype": "thin",
"serviceofferingdetails": {
"domainid": "1"
}
"storagetype": "shared",
"tags": "rbd01"
}
]
}
-----邮件原件-----
发件人: Pierre-Luc Dion <pdion...@apache.org>
发送时间: 2019年11月25日 21:36
收件人: dev@cloudstack.apache.org
主题: Re: vcpu socket configuration
Using cloudmonkey or cmk, you can specify the number of socket at the vm create
using : "details[0].cpu.corespersocket=6"
so if you define 8 vcpu with details[0].cpu.corespersocket=4 the vm will have
4 sockets @2cores.
On Sun, Nov 24, 2019 at 8:41 AM li jerry <div...@hotmail.com> wrote:
> Hello All
>
> We found in the process of use, when the vcpu in service_offering is a
> multiple of 6, vm cpu socket =vcpu/6, when vcpu is a multiple of 4, vm
> cpu
> socket=vcpu/4
>
>
> Excuse me, why do we design this way?
>
> In my application scenario, there are restrictions on cpu socket, so I
> want to lock the socket to cpu socket=vcpu/2, what are the drawbacks?
> (Of course, I will exclude the singular vcpu)
>
>
>
>
> -Jerry
>
