-
Bug
-
Resolution: Done-Errata
-
Normal
-
rhel-9.4
-
libnbd-1.18.1-1.el9
-
None
-
Moderate
-
5c1dae9236d8e3e64a2b669a8503469b1be673c6
-
rhel-sst-virtualization
-
ssg_virtualization
-
23
-
5
-
False
-
-
None
-
None
-
Pass
-
Manual
-
If docs needed, set a value
-
-
Unspecified
-
None
Description of problem:
Upstream NBD has finally accepted a spec change for 64-bit extensions (still listed as experimental until there are enough implementations; but BZ 2182208 tracks implementing the same extensions in qemu). Libnbd has a proof-of-concept implementation that now needs to be polished and incorporated.
https://listman.redhat.com/archives/libguestfs/2022-November/030316.html
Version-Release number of selected component (if applicable):
v1.16
How reproducible:
100%
Steps to Reproduce:
1. Create a 5G image, serve it over qemu-nbd (or qemu-storage-daemon) patched for 64-bit extensions, then use libnbd to connect to it and issue a 64-bit write zero or block status command.
3.
Actual results:
Without extension support, libnbd will flag the request as being oversized
Expected results:
With the extension active in both client and server, requests larger than 32-bit effect length should be possible
Additional info:
- causes
-
RHEL-26717 libnbd fails nbd_can_meta_context with nbd-server 3.25
- In Progress
- depends on
-
RHEL-14476 Rebase libnbd to 1.18.x in RHEL 9.4
- Closed
- external trackers
- links to
-
RHSA-2023:124260 libnbd bug fix and enhancement update