Bug 1860292

Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Hi Kevin,

Could you please kindly handle this? Thanks.

Kevin, we discussed this as part of our planning, can we try to schedule it for 9.2.0 (i.e., Qemu 7.2)? 

Hanna: do you think you could take this?

I don’t see why not.

I guess we can safely clear needinfos and set ITR then. 

Thanks!

Removing the EasyFix tag, because we had some discussion upstream (https://lists.nongnu.org/archive/html/qemu-block/2022-05/msg00062.html), and so given I don’t see one obvious way to implement this, I wouldn’t call it an easy problem to solve.

Advancing stale date by half a year.  There are patches upstream (https://lists.nongnu.org/archive/html/qemu-block/2022-06/msg00466.html).

(In reply to Hanna Reitz from comment #16)
> Advancing stale date by half a year.  There are patches upstream
> (https://lists.nongnu.org/archive/html/qemu-block/2022-06/msg00466.html).

Any updates on the upstream acceptance for said patches? If they are upstream, I suggest we make this BZ "testonly" and make it dependent on a RHEL 9.2 Qemu rebase bz (in case there is one, otherwise we can ask Mirek / John Ferlan for one).

No, no updates yet.

Current status: The patches mentioned in comment 16 are still current, I’ve pinged them on Dec 8 (https://lists.nongnu.org/archive/html/qemu-devel/2022-12/msg01067.html).  Advancing stale date further.

Test on qemu-kvm-7.2.0-8.el9,extent_size_hint can display correctly in qemu-img info xxx.

For qcow2 image:
 1.Create a qcow2 image with extent_size_hint=3.5G
   #qemu-img create -f qcow2 test.img 100G -o extent_size_hint=3.5G
Formatting 'test.img', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=107374182400 lazy_refcounts=off refcount_bits=16 extent_size_hint=3758096384
   #qemu-img info test.img 
image: test.img
file format: qcow2
virtual size: 100 GiB (107374182400 bytes)
disk size: 196 KiB
cluster_size: 65536
Format specific information:
    compat: 1.1
    compression type: zlib
    lazy refcounts: false
    refcount bits: 16
    corrupt: false
    extended l2: false
Child node '/file':
    filename: test.img
    protocol type: file
    file length: 194 KiB (198656 bytes)
    disk size: 196 KiB
    Format specific information:
        extent size hint: 3758096384

 2.Create a qcow2 image with extent_size_hint=0
   #qemu-img create -f qcow2 test.img 100G -o extent_size_hint=0
Formatting 'test.img', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=107374182400 lazy_refcounts=off refcount_bits=16 extent_size_hint=0
   #qemu-img info test.img 
image: test.img
file format: qcow2
virtual size: 100 GiB (107374182400 bytes)
disk size: 196 KiB
cluster_size: 65536
Format specific information:
    compat: 1.1
    compression type: zlib
    lazy refcounts: false
    refcount bits: 16
    corrupt: false
    extended l2: false
Child node '/file':
    filename: test.img
    protocol type: file
    file length: 194 KiB (198656 bytes)
    disk size: 196 KiB

 3.Create a qcow2 image without extent_size_hint
   #qemu-img create -f qcow2 test.img 100G
Formatting 'test.img', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=107374182400 lazy_refcounts=off refcount_bits=16
   #qemu-img info test.img
image: test.img
file format: qcow2
virtual size: 100 GiB (107374182400 bytes)
disk size: 196 KiB
cluster_size: 65536
Format specific information:
    compat: 1.1
    compression type: zlib
    lazy refcounts: false
    refcount bits: 16
    corrupt: false
    extended l2: false
Child node '/file':
    filename: test.img
    protocol type: file
    file length: 194 KiB (198656 bytes)
    disk size: 196 KiB
    Format specific information:
        extent size hint: 1048576

For raw image:
 1.Create a raw image with extent_size_hint=3.5G
   #qemu-img create -f raw test.img 100G -o extent_size_hint=3.5G
Formatting 'test.img', fmt=raw size=107374182400 extent_size_hint=3758096384
   #qemu-img info test.img 
image: test.img
file format: raw
virtual size: 100 GiB (107374182400 bytes)
disk size: 3.5 GiB
Child node '/file':
    filename: test.img
    protocol type: file
    file length: 100 GiB (107374182400 bytes)
    disk size: 3.5 GiB
    Format specific information:
        extent size hint: 3758096384

 2.Create a raw image with extent_size_hint=0
   #qemu-img create -f raw test.img 100G -o extent_size_hint=0
Formatting 'test.img', fmt=raw size=107374182400 extent_size_hint=0
   #qemu-img info test.img 
image: test.img
file format: raw
virtual size: 100 GiB (107374182400 bytes)
disk size: 4 KiB
Child node '/file':
    filename: test.img
    protocol type: file
    file length: 100 GiB (107374182400 bytes)
    disk size: 4 KiB
 
 3. Create raw image without extent_size_hint
    # qemu-img create -f raw test.img 100G
Formatting 'test.img', fmt=raw size=107374182400
    # qemu-img info test.img 
image: test.img
file format: raw
virtual size: 100 GiB (107374182400 bytes)
disk size: 1 MiB
Child node '/file':
    filename: test.img
    protocol type: file
    file length: 100 GiB (107374182400 bytes)
    disk size: 1 MiB
    Format specific information:
        extent size hint: 1048576
 4. Create a small size raw image with large extent_size_hint.
    # qemu-img create -f raw test.img 1G -o extent_size_hint=3.5G
Formatting 'test.img', fmt=raw size=1073741824 extent_size_hint=3758096384
    # qemu-img info test.img 
image: test.img
file format: raw
virtual size: 1 GiB (1073741824 bytes)
disk size: 1 GiB
Child node '/file':
    filename: test.img
    protocol type: file
    file length: 1 GiB (1073741824 bytes)
    disk size: 1 GiB
    Format specific information:
        extent size hint: 3758096384

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

As comment 26 and comment 27, set bug's status to "VERIFIED".

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: qemu-kvm 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-2023:2162