In case this is useful to anyone this is the simplest way I found to
make the cpu_cap parameter change (and some others as well)
echo '{"cpu_cap":NUMBER}' | vmadm update {UUID}
ie:
echo '{"cpu_cap":1200}' | vmadm update 24f5s538-fbd9-4a32-b34f-a32798836ca2
On Wed, Aug 10, 2016 at 5:36 AM, Ian Collins <[email protected]> wrote:
> On 08/10/16 02:40 AM, Humberto Ramirez wrote:
>>>
>>> I think I've earned the dunce's hat for the week.
>>>
>>> The zone on the new box had a cpu_cap of 100, so it was trying to run as
>>> a
>>> one core box... Which is what the "wait" states in prstat where telling
>>> me
>>> all along.
>>>
>>> Change that to 3200 and it builds in half the time as expected.
>>>
>>> --
>>> Ian.
>>>
>> On a system with the configuration below, that number would be 2400
>> cpu_cap relates to the number "CPU Total Cores" is this statement
>> correct?
>>
>
> If you give a VM all 24 "cores", yes.
>
> --
> Ian.
>
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
