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

fsfreeze problems with windows guest

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • No
    • Moderate
    • rhel-virt-windows
    • ssg_virtualization
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

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

      Freeze windows guest filesystem by "virsh domfsfreeze <domain>",  after 10s, try another guest agent command(e.g. virsh domtime <domain>), it says "the command is not allowed".

      Then I do "virsh domfsthaw <domain", it says "couldn't hold writes: fsfreeze is limited up to 10 seconds", but actually the guest filesystem is thawed successfully.

      What is the impact of this issue to you?

      Please provide the package NVR for which the bug is seen:

      virtio-win-1.9.45-0.el10_0.noarch

      qemu-kvm-9.1.0-17.el10.x86_64

      libvirt-11.2.0-1.el10.x86_64

      guest info:

      os.id               : mswindows
      os.name             : Microsoft Windows
      os.pretty-name      : Windows Server 2022 Standard
      os.version          : Microsoft Windows Server 2022
      os.version-id       : 2022
      os.machine          : x86_64
      os.variant          : server
      os.variant-id       : server
      os.kernel-release   : 20348
      os.kernel-version   : 10.0

      How reproducible is this bug?:

      100%

      Steps to reproduce

      1. Start a windows guest, and start qemu-guest-agent service in guest
      2. On host, freeze windows guest filesystems
        # virsh domfsfreeze win2
        Froze 3 filesystem(s)
        
      3.  Within 10s, try a qemu guest agent command, it fails as expected
        # virsh domtime win2
        error: guest agent command failed: unable to execute QEMU agent command 'guest-get-time': Command guest-get-time has been disabled: the command is not allowed
        
      4.  After 10s, guest filesystems should be thawed automatically. Run a qemu guest agent command again. It still failed, which is unexpected:
        # virsh domtime win2
        error: guest agent command failed: unable to execute QEMU agent command 'guest-get-time': Command guest-get-time has been disabled: the command is not allowed
        
      5. Check inside guest, create a new file and save, succeeded.
      6. Thraw the guest filesystems, it reports error. But actually it succeeded(as shown in next step)
        # virsh domfsthaw win2
        error: Unable to thaw filesystems
        error: guest agent command failed: unable to execute QEMU agent command 'guest-fsfreeze-thaw': couldn't hold writes: fsfreeze is limited up to 10 seconds:
        
      7. Run a qemu guest agent command, it succeeded as expected:
        # virsh domtime win2
        Time: 1744973393
        

      Expected results

      10s after windows filesytems are frozen, they should be thrawed automatically, so the following qemu agent commands should succeed

      Actual results

      10s after windows filesytems are frozen, they are thawed when checking inside guest. But the following qemu agent commands failed.

              rh-ee-kkostiuk Kostiantyn Kostiuk
              rhn-support-fjin Fangge Jin
              Kostiantyn Kostiuk Kostiantyn Kostiuk
              Meng Dehan Meng Dehan
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: