Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-24046

FsFreeze windows VM fails but status report frozen

    • None
    • None
    • CustomerScenariosInitiative
    • sst_virtualization
    • ssg_virtualization
    • 5
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None

      What were you trying to do that didn't work?

      I was trying to freeze a windows VM before backing it. The FsFreeze command failed with the following error:

      > `error: Guest agent is not responding: Guest agent not available for now`

      Running fsfreeze status after that shows that the status is "frozen" although the freeze command failed.

      Please provide the package NVR for which bug is seen:

      How reproducible:

      Seems like it is very reproducible right after VM boots

      Steps to reproduce

      1. create windows vm
      2. run 'virsh qemu-agent-command default_fedoravm '{"execute":"guest-fsfreeze-freeze"}' --pretty'
        get return error: `error: Guest agent is not responding: Guest agent not available for now`
      3. run `virsh qemu-agent-command default_fedoravm '{"execute":"guest-fsfreeze-status"}' --pretty`
        get status frozen

      Expected results

      1. The guest agent seems to be ready when we get this error, if its possible to get an error that is more explanatory will be better. (for example if it is the VSS the returns the error then is should be in the error msg)
      2. If freeze fails the status should not change to frozen

      Actual results

      freeze fails and reports frozen

            pkrempa@redhat.com Peter Krempa
            skagan@redhat.com Shelly Kagan
            Peter Krempa Peter Krempa
            Fangge Jin Fangge Jin
            Votes:
            0 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated: