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

[s390x] 'CCW' address is not validated in ABI stability check

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Minor Minor
    • rhel-9.4
    • rhel-9.4
    • libvirt
    • libvirt-9.10.0-1.el9
    • None
    • Low
    • rhel-sst-virtualization
    • ssg_virtualization
    • 17
    • 21
    • None
    • QE ack, Dev ack
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • s390x
    • 9.10.0
    • None

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

      Get a specific error message, like the one on x86_64, when using a migration xml that has some wrong data.

      Please provide the package NVR for which bug is seen:

      libvirt-9.5.0-5.el9.s390x

      How reproducible:

      100%

      Steps to reproduce

      1. Start a VM with an rng device, e.g.
        <rng model='virtio'>
              <backend model='builtin'/>
              <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0009'/>
            </rng>
      1. Migrate the machine, e.g.
        virsh migrate --live --verbose --domain avocado-vt-vm1 --desturi qemu+ssh://10.0.160.6/system --xml /var/tmp/tmp7m3t9yv_

        where the rng device has a different device address, e.g.

        <address type="ccw" cssid="0xfe" ssid="0x0" devno="0x9999" />

      Expected results

      There's an error message, indicating the target address is not matching the source, e.g. on x86_64 for a pci address we'd get

      error: unsupported configuration: Target device PCI address 0000:00:09.01 does not match source 0000:00:09.00

      Given the actual output, maybe the

      Actual results

      Migration: [100.00 %]error: internal error: QEMU unexpectedly closed the monitor (vm='avocado-vt-vm1'): 2023-11-02T08:36:02.208575Z qemu-kvm: Unknown savevm section or instance '/fe.0.0009/virtio-rng' 0. Make sure that your current VM setup matches your saved VM setup, including any hotplugged devices
      2023-11-02T08:36:02.208674Z qemu-kvm: load of migration failed: Invalid argument

              pkrempa@redhat.com Peter Krempa
              smitterl@redhat.com Sebastian Mitterle
              Peter Krempa Peter Krempa
              Sebastian Mitterle Sebastian Mitterle
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: