Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-7543

Windows VM backup procedures blocked with QuiesceFailed errors

XMLWordPrintable

    • Quality / Stability / Reliability
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ToDo
    • Hide

      Issue is more easily reproducible when the VM is under high IO load.

      1. Run Windows VM with virtio drivers and qemu-ga
      2. Run some IO-heavy workload
      3. Create a VM snapshot

      Show
      Issue is more easily reproducible when the VM is under high IO load. 1. Run Windows VM with virtio drivers and qemu-ga 2. Run some IO-heavy workload 3. Create a VM snapshot
    • Very Likely
    • 0
    • Customer Escalated, Customer Facing, Customer Reported
    • 0
    • Unset
    • Unknown
    • None

      Form Initiator: jortialc@redhat.com

      Customer Name: Siemens Numerical Control Ltd.

      Business Impact:

      The VMware-to-OpenShift migration project is a global strategic initiative for Siemens.

      1. This problem blocks the VM backup procedure. No workaround available.
      2. Executive Visibility: Siemens leadership(Director Visibility) is now personally involved and demands resolution immediately.
      3. Financial Impact: This project represents a global TCV of $10.6M ($5.4M ACV), with over $500k in China.

      Due to frequent product instability issues during the recent customer migration process, the user experience has been significantly impacted.

      Escalation Ticket: https://access.redhat.com/watchlist/internal/aces/EN-90945

      Bug Number: https://issues.redhat.com/browse/CNV-74530

      Description:

      Windows VM snapshot operations, either directly or using Velero, fail frequently with QuiesceFailed errors, even if next attempts succeed to freeze the filesystem.

      During a failure we can see these kind of errors in the virt-launcher pod:

      ```

      {"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"28","timestamp":"2026-01-19T08:29:57.915000Z"} {"component":"virt-launcher","level":"error","msg":"Failed to freeze vmi, virError(Code=86, Domain=10, Message='Guest agent is not responding: Guest agent not available for now')","pos":"manager.go:1765","timestamp":"2026-01-19T08:29:57.915712Z"} {"component":"virt-launcher","kind":"","level":"error","msg":"Failed to freeze vmi","name":"snc-server-104ef-acronis-lansweeper","namespace":"vm-it-mgmt","pos":"server.go:269","reason":"virError(Code=86, Domain=10, Message='Guest agent is not responding: Guest agent not available for now')","timestamp":"2026-01-19T08:29:57.915805Z","uid":"2f0b7a0c-c9c4-4d12-aed9-4078e325ad4a"}

      ```

      Related bugs:

      https://issues.redhat.com/browse/CNV-74530 (main)
      https://issues.redhat.com/browse/CNV-54193
      https://issues.redhat.com/browse/CNV-33664

              sseago Scott Seago
              rhn-support-jortialc Juan Orti
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: