Edit Memory, CPU, Autostart, or Watchdog Properties

Using the VM [name] page, Cockpit administrators can access and edit the Memory, CPU, Autostart, or Watchdog properties associated with a VM instance.

What Do You Need?

The Cockpit web console must be installed and accessible.
For details, see these topics: Install and Enable Cockpit and Log in to the Cockpit Web Console.
The Cockpit-machines add-on application must be installed in the web console and the Oracle Linux virtualization packages must be installed and enabled on the host system.
For more information, see Install Cockpit Virtual Machines and Enable Virtualization.
One or more virtual machine instances must already exist on the host system.

Steps

Using the Cockpit web console, follow these steps to view or edit the CPU, Memory, or Autostart properties associated with a VM instance.

In the navigation pane, click Virtual machines, and then click the name of the virtual machine of interest.
The Virtual machines [VM name] page appears.

In Virtual machines [VM name] page, navigate to the Overview section and view or edit any of the following configurable properties:

Memory	To view or edit the memory allocation properties for the selected VM instance, perform the following: Click the edit link. In the Memory adjustment dialog box, view, or edit the memory allocation properties as needed. Click Save, and then restart the VM guest to apply the saved changes.
CPU	Click edit, change the CPU configuration for the VM, click Apply, and then restart the VM guest to apply the saved changes. You can change the following properties: vCPU maximum vCPU count Sockets Cores per socket Threads per core Mode: Select one of the following: Host. When selected, this mode copies the model of the host CPU into the VM Guest definition. For more information, see the libvirt upstream website. Host-passthrough. When selected, this mode presents the VM Guest with a CPU that's the same as the host CPU. Custom. Select an applicable custom mode that defines a normalized CPU that can be migrated throughout dissimilar hosts in a cluster. Note: When performing a live VM migration, the CPU type must be compatible with the target KVM host. Related Information: Understanding CPU topology in Oracle Linux KVM in the Hard Partitioning with Oracle Linux KVM https://www.oracle.com/a/ocom/docs/linux/ol-kvm-hard-partitioning.pdf
Boot order	Click edit, enable the checkbox for any boot source you want to include, then use the arrow buttons to set the boot order.
Autostart	To edit the Autostart property for the selected VM instance, perform the following: Enable or disable the Autostart option. When enabled, the VM guest OS automatically starts upon starting host system.
Watchdog	Note: This feature is only functional when the KVM stack fully caters for USB redirection or PCI passthrough. Requirement: This option requires: 1) installation of watchdog device driver; and 2) the watchdog service enabled and started. To specify Watchdog actions for the selected VM instance, perform the following: Click the add link. In the Watchdog dialog box, specify the action to take if the system stops responding. Click Add.
Vsock	If the host and VM are configured for Vsock support, you can add a Vsock interface. Click the add link, enable Custom identifier, select a number, the click Add.
Firmware	Click the link to select either BIOS or UEFI.

Related Information:

For information on how to restart the VM guest in Cockpit, see Start, Shutdown, Remove, or Interrupt a VM Instance.

For information about virtual hardware in VMs, see Configuring Memory Allocation and Configuring Virtual CPU Count in one of the following locations:

For information about the Watchdog service, see Configuring the Watchdog Service in one of the following locations: