Managing Virtual Machines with Red Hat OpenShift Virtualization

To set the .spec.running or .spec.runStrategy parameters from the command line, edit the VM resource by using the oc edit command:

[user@host ~]$ oc edit vm mariadb-server
# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this
# file will be reopened with the relevant failures.
#
apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
...output omitted...
spec:
  dataVolumeTemplates:
  ...output omitted...
  runStrategy: RerunOnFailure
  template:
    metadata:
...output omitted...

To set the .spec.running or .spec.runStrategy parameters from the Red Hat OpenShift web console, navigate to Virtualization → VirtualMachines.

Select the VM to edit, and navigate to the YAML tab.

Then, use the YAML editor to set the .spec.running or the .spec.runStrategy parameter, and click Save.

You can edit a VM resource to configure health probes. Use the oc edit command to add readinessProbe and livenessProbe sections to the VM resource from the command line. The following example configures a readiness probe for the www1 VM:

[user@host ~]$ oc edit vm www1
# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this
# file will be reopened with the relevant failures.
#
apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
...output omitted...
spec:
  ...output omitted...
  template:
    metadata:
    ...output omitted...
    spec:
      domain:
        ...output omitted...
      readinessProbe:
        httpGet: 
          path: /health
          port: 8080
        initialDelaySeconds: 120 
        periodSeconds: 20  
        timeoutSeconds: 10 
        failureThreshold: 3 
        successThreshold: 3 
...output omitted...

The following example configures a liveness probe for the mariadb-server VM:

[user@host ~]$ oc edit vm mariadb-server
# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this
# file will be reopened with the relevant failures.
#
apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
...output omitted...
spec:
  ...output omitted...
  template:
    metadata:
    ...output omitted...
    spec:
      domain:
        ...output omitted...
      livenessProbe:
        tcpSocket: 
          port: 3306
        initialDelaySeconds: 120
        periodSeconds: 20
...output omitted...

To add health probes from the Red Hat OpenShift web console, navigate to Virtualization → VirtualMachines. Select the VM to edit, and navigate to the YAML tab. Then, use the YAML editor to declare the probes, and click Save.

To activate watchdog monitoring in your VM, add the emulated watchdog device to your VM resource. You can do it by using the oc edit command to add a device section to the VM resource, as follows:

[user@host ~]$ oc edit vm mariadb-server
# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this
# file will be reopened with the relevant failures.
#
apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
...output omitted...
spec:
  ...output omitted...
  template:
    metadata:
    ...output omitted...
    spec:
      domain:
        cpu:
          ...output omitted...
        devices:
          disks:
          - bootOrder: 1
            disk:
              bus: virtio
            name: mariadb-server
          interfaces:
          - macAddress: "02:48:09:00:00:00"
            masquerade: {}
            name: default
          networkInterfaceMultiqueue: true
          rng: {}
          watchdog:
            i6300esb: 
              action: poweroff 
            name: mywatchdog
...output omitted...

To activate watchdog monitoring from the Red Hat OpenShift web console, navigate to Virtualization → VirtualMachines. Select the VM to edit, and navigate to the YAML tab. Then, use the YAML editor to create the watchdog device, and click Save.

Watchdog monitoring works only for operating systems that support the Intel 6300ESB chipset. Red Hat Enterprise Linux automatically loads the kernel module that supports the device.