Chapter 14. Support

Procedure

1. Log in to Red Hat Atlassian Jira.
2. Click the following link to open a Create Issue page: Create issue.
3. Select OpenShift Virtualization (CNV) as the Project.
4. Select Bug as the Issue Type.
5. Click Next.
6. Complete the Summary and Description fields. In the Description field, include a detailed description of the issue.

7. Submit any collected troubleshooting information.

   1. Add any textual troubleshooting information, such as command outputs, in the Description field.
   2. Add troubleshooting files using the Attachment field.
8. Select the appropriate component from Components.
9. Click Create.
10. Review the details of the bug you created.

Procedure

1. To set log verbosity for specific components, open the HyperConverged CR in your default text editor by running the following command:

   $ oc edit hyperconverged kubevirt-hyperconverged -n openshift-cnv

2. Set the log level for one or more components by editing the spec.logVerbosityConfig stanza. For example:

   apiVersion: hco.kubevirt.io/v1beta1
   kind: HyperConverged
   metadata:
     name: kubevirt-hyperconverged
   spec:
     logVerbosityConfig:
       kubevirt:
         virtAPI: 5
         virtController: 4
         virtHandler: 3
         virtLauncher: 2
         virtOperator: 6

   The log verbosity value must be an integer in the range 1–9, where a higher number indicates a more detailed log. In this example, the virtAPI component logs are exposed if their priority level is 5 or higher.

3. Apply your changes by saving and exiting the editor.

Procedure

1. Navigate to Virtualization VirtualMachines.
2. Select a virtual machine to open the VirtualMachine details page.
3. On the General tile, click the pod name to open the Pod details page.
4. Click the Logs tab to view the logs.

Procedure

1. View a list of pods in the OpenShift Virtualization namespace by running the following command:

   $ oc get pods -n openshift-cnv

   Example output:

   NAME                               READY   STATUS    RESTARTS   AGE
   disks-images-provider-7gqbc        1/1     Running   0          32m
   disks-images-provider-vg4kx        1/1     Running   0          32m
   virt-api-57fcc4497b-7qfmc          1/1     Running   0          31m
   virt-api-57fcc4497b-tx9nc          1/1     Running   0          31m
   virt-controller-76c784655f-7fp6m   1/1     Running   0          30m
   virt-controller-76c784655f-f4pbd   1/1     Running   0          30m
   virt-handler-2m86x                 1/1     Running   0          30m
   virt-handler-9qs6z                 1/1     Running   0          30m
   virt-operator-7ccfdbf65f-q5snk     1/1     Running   0          32m
   virt-operator-7ccfdbf65f-vllz8     1/1     Running   0          32m

2. View the pod log by running the following command:

   $ oc logs -n openshift-cnv <pod_name>

   Note

   If a pod fails to start, you can use the --previous option to view logs from the last attempt.

   To monitor log output in real time, use the -f option.

   Example output:

   {"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:453","timestamp":"2022-04-17T08:58:37.373695Z"}
   {"component":"virt-handler","level":"info","msg":"set verbosity to 2","pos":"virt-handler.go:453","timestamp":"2022-04-17T08:58:37.373726Z"}
   {"component":"virt-handler","level":"info","msg":"setting rate limiter to 5 QPS and 10 Burst","pos":"virt-handler.go:462","timestamp":"2022-04-17T08:58:37.373782Z"}
   {"component":"virt-handler","level":"info","msg":"CPU features of a minimum baseline CPU model: map[apic:true clflush:true cmov:true cx16:true cx8:true de:true fpu:true fxsr:true lahf_lm:true lm:true mca:true mce:true mmx:true msr:true mtrr:true nx:true pae:true pat:true pge:true pni:true pse:true pse36:true sep:true sse:true sse2:true sse4.1:true ssse3:true syscall:true tsc:true]","pos":"cpu_plugin.go:96","timestamp":"2022-04-17T08:58:37.390221Z"}
   {"component":"virt-handler","level":"warning","msg":"host model mode is expected to contain only one model","pos":"cpu_plugin.go:103","timestamp":"2022-04-17T08:58:37.390263Z"}
   {"component":"virt-handler","level":"info","msg":"node-labeller is running","pos":"node_labeller.go:94","timestamp":"2022-04-17T08:58:37.391011Z"}

Procedure

1. From the side menu, click Virtualization Overview.
2. Click the Settings tab.
3. Click Cluster Guest management.
4. Set Enable guest system log access to on.
5. Optional: If you want to hide the VM user credentials that were set by using cloud-init, set Hide guest credentials for non-privileged users to on.

Procedure

1. Open the HyperConverged CR in your default editor by running the following command:

   $ oc edit hyperconverged kubevirt-hyperconverged -n openshift-cnv

2. Update the disableSerialConsoleLog value. For example:

   kind: HyperConverged
   metadata:
     name: kubevirt-hyperconverged
   spec:
     virtualMachineOptions:
       disableSerialConsoleLog: true
   #...

   Set the value of disableSerialConsoleLog to false if you want serial console access to be enabled on VMs by default.

Procedure

1. Click Virtualization VirtualMachines from the side menu.
2. Select a virtual machine to open the VirtualMachine details page.
3. Click the Configuration tab.
4. Set Guest system log access to on or off.

Procedure

1. Edit the virtual machine manifest by running the following command:

   $ oc edit vm <vm_name>

2. Update the value of the logSerialConsole field. For example:

   apiVersion: kubevirt.io/v1
   kind: VirtualMachine
   metadata:
     name: example-vm
   spec:
     template:
       spec:
         domain:
           devices:
             logSerialConsole: true
   #...

   To enable access to the guest serial console log, set the logSerialConsole value to true.

3. Apply the new configuration to the VM by running the following command:

   $ oc apply vm <vm_name>

4. Optional: If you edited a running VM, restart the VM to apply the new configuration. For example:

   $ virtctl restart <vm_name> -n <namespace>

Procedure

1. Click Virtualization VirtualMachines from the side menu.
2. Select a virtual machine to open the VirtualMachine details page.
3. Click the Diagnostics tab.
4. Click Guest system logs to load the serial console.

Procedure

1. Navigate to Observe Logs in the web console.
2. Select application, for virt-launcher pod logs, or infrastructure, for OpenShift Virtualization control plane pods and containers, from the log type list.
3. Click Show Query to display the query field.
4. Enter the LogQL query in the query field and click Run Query to display the filtered logs.