Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-34884

Missing qemu log error at at virt-handler/launcher or virtualmachinemigration status

XMLWordPrintable

    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • ---
    • ---
    • No

      Description of problem:

      At some scenarios live migration is failing and the error is down deep at /var/run/kubevirt-private/libvirt/qemu/, the content of this error should be show at some k8s resources, ideally at virtualmachineinstance status.

      Version-Release number of selected component (if applicable):

      4.15

      How reproducible:

      Always

      Steps to Reproduce:

      1. Startup hypershift kubevirt cluster at aws with 2 infra nodes and three guest nodes
2. Run conformance tests with --run "StatefulSet Non-retain" 
3. Run live-migration of one of the workers

      Actual results:

      Live migration failures without clear view of what's the error

      Expected results:

      The content of /var/run/kubevirt-private/libvirt/qemu/ should be present at some of the cnv k8s resources

      Additional info:

      This is the qemu error

2023-10-30T19:53:14.880648Z qemu-kvm: qemu_savevm_state_complete_precopy_non_iterable: bdrv_inactivate_all() failed (-1)
2023-10-30T19:53:15.053395Z qemu-kvm: Unable to read from socket: Bad file descriptor

              ellorent Felix Enrique Llorente Pastora
              ellorent Felix Enrique Llorente Pastora
              Kedar Bidarkar Kedar Bidarkar
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: