Page History

Add_workflow_for_techpubs

AUTH1	UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTH	CHOR-362
REV5	UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6	UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c99e02c0, userName='null'}
REV1	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c7f3007b, userName='null'}

Panel

In this section:

Table of Contents

maxLevel	4

...

Login into a terminal access software (such as Putty), and log into the KVM server.
Start the Virtual Machine Manager.
From the list, click on the applicable VM instance.
Power down the VM.
Select Edit > Virtual Machine Details
Select View > Details or click the icon
From the menu, click CPUs.The SWe Lite supports 1, 2, or 4 vCPUs.
Pagebreak
Caption
0 Figure
1 Add vCPUs
Click Apply.
From the menu, click Memory. Each SWe Lite instance with 1 vCPU requires 1 GiB (1024 MiB) RAM; this amount is increased according to the number of vCPUs. Refer to SBC SWe Lite Hardware and Software Requirements.
Caption
0 Figure
1 Update Memory
Click Apply.
Start the VM instance. The SWe Lite is configured with the updated values.