> 1. What is the scope of harm if this BZ is not resolved in this release?  Reviewers want to know which RHEL features or customers are affected and if it will impact any Layered Product or Hardware partner plans.

Everything related to virt-v2v & libguestfs will be broken.  We need to fix whatever
is the issue.

> 2. What are the risks associated with resolving this BZ?  Reviewers want to know the scope of retesting, potential regressions

Retesting, but nothing else.

> 3. Provide any other details that meet blocker criteria or should be weighed in making a decision (Other releases affected, upstream status, business impacts, etc).

See discussion in https://bugzilla.redhat.com/show_bug.cgi?id=2034160 since
it seems to be caused by the same issue (upgrading to qemu 6.2).

Same comment as here:
https://bugzilla.redhat.com/show_bug.cgi?id=2034160#c35

"I ACKed the patch.  Do you want to do the build?  If it's urgent and you can't
do it then I could do it today, but would prefer to wait until Jan.  There is
a workaround (downgrading to qemu 6.1) but that's not too nice because we
ought to be testing if there are any other problems with 6.2."

Reproduce with packages:
libguestfs-1.44.0-4.module+el8.6.0+12969+f61072d9.x86_64
qemu-kvm-6.2.0-1.module+el8.6.0+13725+61ae1949.x86_64

Steps:

1. On rhel8.6 host
# guestfish --network run
libguestfs: error: could not create appliance through libvirt.

Try running qemu directly without libvirt using this environment variable:
export LIBGUESTFS_BACKEND=direct

Original error from libvirt: internal error: qemu unexpectedly closed the monitor: 2021-12-27T06:09:49.081270Z qemu-kvm: -device {"driver":"virtio-scsi-pci","id":"scsi0","bus":"pci.0","addr":"0x2"}: PCI: slot 2 function 0 not available for virtio-scsi-pci, in use by virtio-net-pci [code=1 int1=-1]

2.
# virt-customize -a RHEL-Server-8.3.0-64-hvm.raw --mkdir /root/test1
[   0.0] Examining the guest ...
virt-customize: error: libguestfs error: could not create appliance through 
libvirt.

Try running qemu directly without libvirt using this environment variable:
export LIBGUESTFS_BACKEND=direct

Original error from libvirt: internal error: qemu unexpectedly closed the 
monitor: 2021-12-27T06:12:02.108822Z qemu-kvm: -device 
{"driver":"virtio-scsi-pci","id":"scsi0","bus":"pci.0","addr":"0x2"}: PCI: 
slot 2 function 0 not available for virtio-scsi-pci, in use by 
virtio-net-pci [code=1 int1=-1]



Test with fixed packages:
libguestfs-1.44.0-5.module+el8.6.0+13732+b2b9b31d.x86_64
qemu-kvm-6.2.0-1.module+el8.6.0+13725+61ae1949.x86_64


Steps:

1.
# guestfish --network run 

2.
# virt-customize -a RHEL-Server-8.3.0-64-hvm.raw --mkdir /root/test1
[   0.0] Examining the guest ...
[   6.4] Setting a random seed
[   6.4] Making directory: /root/test1
[   6.5] Finishing off

No error output

Reset Verified:Tested as errata_automation bot ran into issues.

Seems the errata_automation bot needs a whole fixed version.

Verified this bug since it is fixed when running libguestfs autotest with the latest RHEL9 compose

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: virt:rhel and virt-devel:rhel security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:1759