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

filesystem info returned by guest agent is different from that in the guest under image mode

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

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • rhel-10.2
    • qemu-kvm / Guest Agent
    • None
    • None
    • None
    • rhel-virt-core
    • 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?

      filesystem info returned by guest agent is different from that in the guest under image mode

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

      qemu-guest-agent-10.1.0-13.el10.x86_64
      libvirt-11.10.0-10.el10.x86_64

      How reproducible is this bug?:

      100%

      Steps to reproduce:
      1. Check the guest filesystem info via libvirt qemu-agent-command

      # virsh qemu-agent-command avocado-vt-vm1 '{"execute":"guest-get-fsinfo"}' --pretty 
      {
        "return": [
          {
            "name": "vda2",
            "total-bytes": 525033472,
            "total-bytes-privileged": 525033472,
            "mountpoint": "/boot/efi",
            "disk": [
              {
                "bus-type": "virtio",
                "bus": 0,
                "unit": 0,
                "pci-controller": {
                  "bus": 4,
                  "slot": 0,
                  "domain": 0,
                  "function": 0
                },
                "dev": "/dev/vda2",
                "target": 0
              }
            ],
            "used-bytes": 9412608,
            "type": "vfat"
          },
          {
            "name": "vda3",
            "total-bytes": 1006632960,
            "total-bytes-privileged": 1006632960,
            "mountpoint": "/boot",
            "disk": [
              {
                "bus-type": "virtio",
                "bus": 0,
                "unit": 0,
                "pci-controller": {
                  "bus": 4,
                  "slot": 0,
                  "domain": 0,
                  "function": 0
                },
                "dev": "/dev/vda3",
                "target": 0
              }
            ],
            "used-bytes": 315019264,
            "type": "xfs"
          },
          {
            "name": "vda4",
            "total-bytes": 9069113344,
            "total-bytes-privileged": 9069113344,
            "mountpoint": "/etc",
            "disk": [
              {
                "bus-type": "virtio",
                "bus": 0,
                "unit": 0,
                "pci-controller": {
                  "bus": 4,
                  "slot": 0,
                  "domain": 0,
                  "function": 0
                },
                "dev": "/dev/vda4",
                "target": 0
              }
            ],
            "used-bytes": 3167854592,
            "type": "xfs"
          }
        ]
      }
      

      2. Check the filesystem info in guest

      # lsblk 
      NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
      vda    252:0    0   10G  0 disk 
      ├─vda1 252:1    0    1M  0 part 
      ├─vda2 252:2    0  501M  0 part /boot/efi
      ├─vda3 252:3    0    1G  0 part /boot
      └─vda4 252:4    0  8.5G  0 part /var
                                      /sysroot/ostree/deploy/default/var
                                      /sysroot
                                      /etc
      

      Actual results

      filesystem info returned by guest agent is different from that in the guest under image mode. There are more mountpoints for vda4 in the guest.

      Question:

      • Is the result of guest-get-fsinfo still meaningful in image mode?
      • If it is for the above the question, then is the current result correct?

              virt-maint virt-maint
              rhn-support-lizhu Lili Zhu
              virt-maint virt-maint
              virt-bugs virt-bugs
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: