oakcli configure vm

Use the oakcli configure vm command to configure a virtual machine on Oracle Database Appliance Virtualized Platform and to increase or decrease resource allocation to user domains.

You must restart the domain for the resource allocation change to take effect.

Syntax

oakcli configure vm name [-vcpu cpucount -maxvcpu maxcpu -cpuprio priority 
-cpucap cap -memory memsize -maxmemory max_memsize -os sys -keyboard lang -mouse 
mouse_type -domain dom -network netlist -autostart astart -disk disks -bootoption
bootstrap -cpupool pool -prefnode 0|1 -failover true|false][-h]

Parameters

Parameter	Description
`name`	The name assigned to the virtual machine.
`-vcpu` `cpucount`	Number of nodes assigned to the virtual machine. The range is 1 to 72. This number depends on your Oracle Database Appliance configuration: On Oracle Database Appliance X5-2, the range is from 1 to 72. On Oracle Database Appliance X4-2, the range is from 1 to 48. On Oracle Database Appliance X3-2, the range is from 1 to 32. On Oracle Database Appliance, the range is 1 to 24.
`-maxvcpu` `maxcpu`	Maximum number of CPUs that the virtual machine can consume. The range is 1 to 72. This number depends on your Oracle Database Appliance configuration: On Oracle Database Appliance X5-2, the range is from 1 to 72. On Oracle Database Appliance X4-2, the range is from 1 to 48. On Oracle Database Appliance X3-2, the range is from 1 to 32. On Oracle Database Appliance version 1, the range is 1 to 24.
`-cpuprio` `priority`	Priority for CPU usage, where larger values have higher priority. The range is 1 to 65535.
`-cpucap` `cap`	Percentage of a CPU the virtual machine can receive. The range is 10 to 100.
`-memory` `memsize`	Amount of memory given to the virtual machine: (1 to 248)G to (1to 760G) or (1 to 253952)M to (1 to 778240)M, based on RAM. The default is M.
`-maxmemory` `max_memsize`	Maximum amount of memory allowed for the virtual machine: (1 to 248)G to (1 to 760)G or (1-253952)M to (1-778240)M, based on RAM. The default is M.
`-os` `sys`	Operating system used by the virtual machine (WIN_2003, WIN_2008, WIN_7, WIN_VISTA, OTHER_WIN, OL_4, OL_5, OL_6, RHL_4, RHL_5, RHL_6, LINUX_RECOVERY, OTHER_LINUX, SOLARIS_10, SOLARIS_11, OTHER_SOLARIS, or NONE)
`-keyboard` `lang`	Keyboard used by virtual machine (en-us, ar, da, de, de-ch, en-gb, es, et, fi, fo, fr, fr-be, fr-ca, hr, hu, is, it, ja, lt, lv, mk, nl, n--be, no, pl, pt, pt-br, ru, sl, sv, th, or tr)
`-mouse` `mouse_type`	Mouse type used by the virtual machine (OS_DEFAULT, PS2_MOUSE, USB_MOUSE, or USB_TABLET)
`-domain` `dom`	Domain type from the following options: Hardware virtualized guest (XEN_HVM) - The kernel or operating system is not virtualization-aware and can run unmodified. - Device drivers are emulated. Para virtualized guest (XEN_PVM) - The guest is virtualization-aware and is optimized for a virtualized environment. - PV guests use generic, idealized device drivers. Hardware virtualized guest (XEN_HVM_PV_DRIVERS) The PV drivers are hypervisor-aware and significantly reduce the overhead of emulated device input/output. Hardware virtualized guest (UNKNOWN)
`-network` `netlist`	MAC address and list of networks used by the virtual machine
`-autostart` `astart`	Startup option for virtual machine (always, restore, or never)
`-disk` `disks`	List of disks (slot, disktype, and content) used by virtual machine
`-bootoption` `bootstrap`	Boot option used to bootstrap the virtual machine (PXE, DISK, or CDROM)
`-cpupool` `pool`	Named CPU pool assigned to the virtual machine
`-prefnode 0\|1`	Preferred node on which the virtual machine will attempt to start (Node 0 or Node 1). This parameter is only valid for virtual machines created in shared repositories.
`-failover true\|false`	Allow (use the keyword "true") or disallow (use the keyword "false") the virtual machine to start or restart on a node other than the node defined by the `-prefnode` parameter. This parameter is only valid for virtual machines created in shared repositories.
`-h`	(Optional) Display help for using the command.

Usage Notes

All of the parameters, except for name, are optional.
You must include at least one optional parameter for the command to work.
When you create a virtual machine, select the Processor Cap as a percentage, between 10 and 100%. The default is 100%. This value is then converted to a CPU utilization limit in the vm.cfg file for the virtual machine. The value set in the vm.cfg file limits the amount of CPU a guest is allowed to consume. If the Processor Cap is set at 100% in Oracle VM, then the value set in vm.cfg is 0, which means there is no limit to CPU utilization.