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

[virtio shutdown] qemu reports "virtio: zero sized buffers are not allowed" in "virsh reboot vm" for vm protected by smmuv3

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Yes
    • Low
    • 2
    • rhel-virt-hwe-arm-1
    • ssg_virtualization
    • 1
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • Virt ARM 25-4, Split items
    • Pass
    • New Test Coverage
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      Based Copied from - on : https://issues.redhat.com/browse/RHEL-26264

      What were you trying to do that didn't work?
      When the guest uses virtio-scsi controller and is protected with smmuv3, after reboot the guest e.g. via "virsh reboot vm", the qemu process will report a message: "virtio: zero sized buffers are not allowed".

      libvirt libvirt-10.10.0-9.el9.aarch64
      qemu-kvm qemu-kvm-9.1.0-17.el9.aarch64
      kernel kernel-5.14.0-573.el9.aarch64+64k
      edk2-aarch64 edk2-aarch64-20241117-3.el9.noarch

      How reproducible:
      always

      Steps to reproduce:
      1) prepare VM and start a SCSI guest with smmuv3 protection and iommu_platform=on into virtio-scsi device (e.g. virsh define vm2a.xml)

      2) wait till the vm2 starts
      3) run virsh reboot vm2
      4) check qemu report ( /var/log/libvirt/qemu/vm2.log )

      Expected results
      Guest rebooted without anything

      Actual results
      qemu reports:

      qemu-kvm: virtio: zero sized buffers are not allowed
      
      

              eauger Eric Auger
              rh-ee-hholoubk Hana Holoubkova
              virt-maint virt-maint
              Hana Holoubkova Hana Holoubkova
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: