Re: vcpu socket configuration

2019-11-25 Thread Pierre-Luc Dion
ng coresPerSocket = details.get(" cpu.corespersocket"); > > This is vmware: > String coresPerSocket = vmSpec.getDetails().get("cpu.corespersocket"); > > 发件人: Nii Apleh Lartey > 发送时间: 2019年11月25日 22:07 > 收件人: li jerry ; dev@cloudstack.apache.org > 主题: Re: vcpu

回复: vcpu socket configuration

2019-11-25 Thread li jerry
i Apleh Lartey 发送时间: 2019年11月25日 22:07 收件人: li jerry ; dev@cloudstack.apache.org 主题: Re: vcpu socket configuration Sorry, Try using "cpuid.coresPerSocket" instead -- Nii From: li jerry mailto:div...@hotmail.com>> Sent: Monday, November 25, 2019 2

Re: vcpu socket configuration

2019-11-25 Thread Pierre-Luc Dion
"netmask": "255.255.255.0", > "networkid": "e28d44cf-9179-4526-81b6-990ef31ec9be", > "networkname": "test-assistanz-mon", > "secondaryip": [], > "traffictype": "Guest&qu

Re: vcpu socket configuration

2019-11-25 Thread Nii Apleh Lartey
Sorry, Try using "cpuid.coresPerSocket" instead -- Nii From: li jerry Sent: Monday, November 25, 2019 2:02 PM To: dev@cloudstack.apache.org Subject: 回复: vcpu socket configuration After deploying the VM with the following command, the cpu socke

回复: vcpu socket configuration

2019-11-25 Thread li jerry
t", "type": "Isolated" } ], "ostypeid": "c7a858b6-e184-11e8-9d95-4ab2a88c1305", "passwordenabled": true, "rootdeviceid": 0, "rootdevicetype": "ROOT", "secur

Re: vcpu socket configuration

2019-11-25 Thread Nii Apleh Lartey
You have a "p" and the end of "details" From: li jerry Sent: Monday, November 25, 2019 1:52 PM To: dev@cloudstack.apache.org Subject: 回复: vcpu socket configuration Thank you, Socket doesn't work after I deploy VM with the follow

回复: vcpu socket configuration

2019-11-25 Thread li jerry
ot;SP01-20C4G", "offerha": true, "provisioningtype": "thin", "serviceofferingdetails": { "domainid": "1" } "storagetype": "shared", "tags": "rbd01" } ] } -邮件原件- 发件人: Pierre-Luc

Re: vcpu socket configuration

2019-11-25 Thread Pierre-Luc Dion
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 wrote: > Hello All > > We found in

vcpu socket configuration

2019-11-24 Thread li jerry
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 t