Syncrhonized BZs in qemu-kvm-6.0.0-5.el9:
 - 1929720: [aarch64] Handle vsmmuv3 IOTLB invalidation with non power of 2 size
 - 1927108: It's too slow to load scsi disk when use 384 vcpus
 - 1957667: [aarch64] Add 8.5 machine type
 - 1953045: qemu-kvm NULL pointer de-reference during migration at migrate_fd_connect ->...-> notifier_list_notify
 - 1957834: [ppc64le] RHEL AV 8.5 new machine type for ppc64le
 - 1951476: [s390x] RHEL AV 8.5 new machine type for s390x
 
 Tested only BZs to test with qemu-kvm-6.0.0-5.el9
 - 1923881

Hi Mirek,

I see this bz as in build qemu-kvm-6.0.0-5:

- Resolves: bz#1957194
  (Synchronize RHEL-AV 8.5.0 changes to RHEL 9.0.0 Beta)

(https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1626248)

'Fixed in version' does not use this build now.  Is it because this it is a tracker bz and other dependence bzs will be added later ?

Thanks!

(In reply to Yanan Fu from comment #3)
> Hi Mirek,
> 
> I see this bz as in build qemu-kvm-6.0.0-5:
> 
> - Resolves: bz#1957194
>   (Synchronize RHEL-AV 8.5.0 changes to RHEL 9.0.0 Beta)
> 
> (https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1626248)
> 
> 'Fixed in version' does not use this build now.  Is it because this it is a
> tracker bz and other dependence bzs will be added later ?
> 
> Thanks!

Yes,

this is BZ used for doing synchronization so we do not need RHEL 9 clones for RHEL-AV 8 BZs. Whenever new changes are done in RHEL-AV 8.5 and I synchronize them, I'll add new fixes info in this BZ as a comment like this time. Plan is to stop syncing on DTM when BZ will move to modified (maybe directly to ON_QA).

(In reply to Miroslav Rezanina from comment #4)
> (In reply to Yanan Fu from comment #3)
> 
> Yes,
> 
> this is BZ used for doing synchronization so we do not need RHEL 9 clones
> for RHEL-AV 8 BZs. Whenever new changes are done in RHEL-AV 8.5 and I
> synchronize them, I'll add new fixes info in this BZ as a comment like this
> time. Plan is to stop syncing on DTM when BZ will move to modified (maybe
> directly to ON_QA).

Got it, thanks for your explanation !

Syncrhonized BZs in qemu-kvm-6.0.0-6.el9:

- 1965626: RHEL8.2 - QEMU BIOS fails to read stage2 loader (kvm)
- 1966463: Rebuild the s390-netboot.img for downstream instead of shipping the upstream image
- 1967177: QEMU 6.0.0 socket_get_fd() fails with the error "socket_get_fd: too many connections"
- 1957022: SEV: Add support to query the attestation report
- 1960119: [regression]Failed to reset guest
- 1942914: [Hyper-V][RHEL8.4]Nested Hyper-V on KVM: On Intel CPU L1 2016 can not start with cpu model Skylake-Server-noTSX-IBRS or Skylake-Client-noTSX-IBRS
- 1940731: [ppc64le] Hotplug vcpu device hit call trace:[qemu output] KVM: unknown exit, hardware reason 7fff9ce87ed8

Synchronized BZs in qemu-kvm-6.0.0-7.el9:

- 1957838 8.5 machine types for x86
- 1967603 Enable interrupt based asynchronous page fault mechanism by default
- 1960137 [incremental backup] qemu-kvm hangs when Rebooting the VM during full backup
- 1866133 Disable usb-bot device in QEMU (unsupported)
- 1954750 firmware scheme for sev-es

Synchronized BZs in qemu-kvm-6.0.0-9.el9:

- 1976015 spapr: Fix EEH capability issue on KVM guest for PCI passthru
- 1789757 [IBM 8.5 FEAT] Add machine option to enable secure VM support
- 1950405 review qemu-kvm-core dependencies
- 1804196 inconsistent paths for interop json files

Synchronized BZs in qemu-kvm-6.0.0-10.el9

- 1943653 RHV VM pauses due to 'qemu-kvm' getting EINVAL on i/o to a direct lun with scsi passthrough enabled
- 1935014 qemu crash when attach vhost-user-blk-pci with option queue-size=4096
- 1935019 qemu guest failed boot when attach vhost-user-blk-pci with option iommu_platform=on
- 1935020 qemu guest failed boot when attach vhost-user-blk-pci with option packed=on
- 1935031 qemu guest failed boot when attach vhost-user-blk-pci with unmatched num-queues with qsd
- 1968326 [vfio_ccw] I/O error when checking format - dasdfmt requires --force in quick mode when passed through

*** Bug 1989601 has been marked as a duplicate of this bug. ***

Synchronized BZs in qemu-kvm-6.0.0-12.el9:

- 1977798 RHEL8.5 guest network interface name changed after upgrade to qemu-6.0
- 1787194 After canceling the migration of a vm with VF which enables failover, using "migrate -d tcp:invalid uri" to re-migrating the vm will cause the VF in vm to be hot-unplug.
- 1959676 guest status is paused after loadvm on rhel8.5.0
- 1959729 SAP/3TB VM migration slowness [idle db]
- 1924822 [Intel 8.5 FEAT] qemu-kvm AVX2 VNNI - Fast Train
- 1838221 [Intel 8.5 FEAT]  qemu-kvm Bus Lock VM Exit - Fast Train
- 1930286 randread and randrw regression with virtio-blk multi-queue
- 1848881 nvme:// block driver can exhaust IOMMU DMAs, hanging the VM, possible data loss
- 1976852 [failover vf migration] The failover vf will be unregistered  if canceling the migration whose status is "wait-unplug"
- 1974579 It's not possible to start installation from a virtual USB device on aarch64
- 1946084 qemu-img convert --bitmaps fail if a bitmap is inconsistent
- 1991671 vmstate differs between -audiodev and QEMU_AUDIO_DRV when no sound frontends devs present.


This is last synchronization from RHEL-AV 8.5.0.

QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass.

Passed retest on
Red Hat Enterprise Linux release 9.0 Beta (Plow)
5.14.0-0.rc6.46.el9.x86_64
qemu-kvm-common-6.0.0-12.el9.x86_64

https://bugzilla.redhat.com/show_bug.cgi?id=1935014
https://bugzilla.redhat.com/show_bug.cgi?id=1935019
https://bugzilla.redhat.com/show_bug.cgi?id=1935020
https://bugzilla.redhat.com/show_bug.cgi?id=1935031
https://bugzilla.redhat.com/show_bug.cgi?id=1943653