Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
There is new export type in qsd help message:
--export [type=]vduse-blk,id=<id>,node-name=<node-name>
,name=<vduse-name>[,writable=on|off]
[,num-queues=<num-queues>][,queue-size=<queue-size>]
[,logical-block-size=<logical-block-size>]
[,serial=<serial-number>]
export the specified block node as a
vduse-blk device
But the type need kernel support and may be used in QEMU.
So far, the type is not supported in QEMU.
Version-Release number of selected component (if applicable):
qemu-storage-daemon version 7.1.0 (qemu-kvm-7.1.0-1.el9)
How reproducible:
100%
Steps to Reproduce:
1.qemu-storage-daemon -h
2.
3.
Actual results:
Find unsupported export type in QEMU
Expected results:
Hide unsupported export type
Additional info:
Passed test on 7.2.0-7.el9
qemu-storage-daemon -V
qemu-storage-daemon version 7.2.0 (qemu-kvm-7.2.0-7.el9)
root@dell-per440-07 /tmp/qemu7-7 $ qemu-storage-daemon -h
Usage: qemu-storage-daemon [options]
QEMU storage daemon
-h, --help display this help and exit
-T, --trace [[enable=]<pattern>][,events=<file>][,file=<file>]
specify tracing options
-V, --version output version information and exit
--blockdev [driver=]<driver>[,node-name=<N>][,discard=ignore|unmap]
[,cache.direct=on|off][,cache.no-flush=on|off]
[,read-only=on|off][,auto-read-only=on|off]
[,force-share=on|off][,detect-zeroes=on|off|unmap]
[,driver specific parameters...]
configure a block backend
--chardev <options> configure a character device backend
(see the qemu(1) man page for possible options)
--daemonize daemonize the process, and have the parent exit
once startup is complete
--export [type=]nbd,id=<id>,node-name=<node-name>[,name=<export-name>]
[,writable=on|off][,bitmap=<name>]
export the specified block node over NBD
(requires --nbd-server)
--export [type=]vhost-user-blk,id=<id>,node-name=<node-name>,
addr.type=unix,addr.path=<socket-path>[,writable=on|off]
[,logical-block-size=<block-size>][,num-queues=<num-queues>]
export the specified block node as a
vhost-user-blk device over UNIX domain socket
--export [type=]vhost-user-blk,id=<id>,node-name=<node-name>,
addr.type=fd,addr.str=<fd>[,writable=on|off]
[,logical-block-size=<block-size>][,num-queues=<num-queues>]
export the specified block node as a
vhost-user-blk device over file descriptor
--monitor [chardev=]name[,mode=control][,pretty[=on|off]]
configure a QMP monitor
--nbd-server addr.type=inet,addr.host=<host>,addr.port=<port>
[,tls-creds=<id>][,tls-authz=<id>][,max-connections=<n>]
--nbd-server addr.type=unix,addr.path=<path>
[,tls-creds=<id>][,tls-authz=<id>][,max-connections=<n>]
start an NBD server for exporting block nodes
--object help list object types that can be added
--object <type>,help list properties for the given object type
--object <type>[,<property>=<value>...]
create a new object of type <type>, setting
properties in the order they are specified. Note
that the 'id' property must be set.
See the qemu(1) man page for documentation of the
objects that can be added.
--pidfile <path> write process ID to a file after startup
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
Description of problem: There is new export type in qsd help message: --export [type=]vduse-blk,id=<id>,node-name=<node-name> ,name=<vduse-name>[,writable=on|off] [,num-queues=<num-queues>][,queue-size=<queue-size>] [,logical-block-size=<logical-block-size>] [,serial=<serial-number>] export the specified block node as a vduse-blk device But the type need kernel support and may be used in QEMU. So far, the type is not supported in QEMU. Version-Release number of selected component (if applicable): qemu-storage-daemon version 7.1.0 (qemu-kvm-7.1.0-1.el9) How reproducible: 100% Steps to Reproduce: 1.qemu-storage-daemon -h 2. 3. Actual results: Find unsupported export type in QEMU Expected results: Hide unsupported export type Additional info: