![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||
Solution Type Problem Resolution Sure Solution 1928868.1 : Guest VM Running Slow and is not Able to Use All the CPUs Assigned to it on ODA
In this Document
Created from <SR 3-9553616971> Applies to:Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]Information in this document applies to any platform. SymptomsAfter creating Guest VM on ODA VM setup, they are running very slow.
The top command in guest VM shows following: top - 07:51:49 up 11 days, 12:42, 1 user, load average: 3.22, 4.20, 3.22
Tasks: 519 total, xx running, 518 sleeping, 0 stopped, 0 zombie Cpu(s): 30%us, 40%sy, 0.0%ni, 30%id, 1.2%wa, 0.0%hi, 0.0%si, 60 %st <<<<<<<< %st will be aroung 60 to 80 which is actually Mem: 32488228k total, 31498624k used, 989604k free, 514032k buffers Swap: 20477948k total, 26192k used, 20451756k free, 10637544k cached
% st = steal (time given to other DomU instances)
Following is the VM info from oakcli command from DOM1 ODA BASE :
$ oakcli show vm NAME NODENUM MEMORY VCPU STATE REPOSITORY ovp-v-webpd2 0 26624 8 ONLINE samplerepo
$ oakcli show vm ovp-v-webpd2
Following is the xmtop output from Dom 0:
xentop - 07:26:04 Xen 4.1.3OVM NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%)
xm sched-credit from Dom 0:
$ xm sched-credit
ChangesA new guest VM was imported and created in ODA virtualized machine. CauseCPU_CAP for the guest VM is set to 100 which means regardless of CPU assigned to this virtual machine, it will only use 1 CPU. Solution> Execute following command to dynamically change the CPU_CAP from DOM 0: $ xm sched-credit -d <vm name> -c 0
> Also change the following file for permanently changing the CPU_CAP for virtual machine: /OVS/Repositories/samplerepo/VirtualMachines/<vm name>/vm.cfg change : cpu_cap = 100 to cpu_cap = 0
A new internal unpublished bug has been created so that cpu_cap can be set to 0 using oakcli command line itself. Currently it does not allow this to set it to 0. Bug 19593517 - LNX64-11.2-CMT : INCORRECT CPU CAP SETTINGS References<BUG:19593517> - LNX64-11.2-CMT : INCORRECT CPU CAP SETTINGSAttachments This solution has no attachment |
||||||||||||||||||||
|