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.
Bug 2038045 - Documentation about using virt-admin to manage other daemons should be added
Summary: Documentation about using virt-admin to manage other daemons should be added
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Peter Krempa
QA Contact: Lili Zhu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-07 07:33 UTC by Lili Zhu
Modified: 2022-11-15 10:36 UTC (History)
5 users (show)

Fixed In Version: libvirt-8.1.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 10:03:03 UTC
Type: Bug
Target Upstream Version: 8.1.0
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-107059 0 None None None 2022-01-07 07:39:13 UTC
Red Hat Product Errata RHSA-2022:8003 0 None None None 2022-11-15 10:03:22 UTC

Description Lili Zhu 2022-01-07 07:33:46 UTC 
Description of problem:
Instead of virtproxyd/libvirtd/admin, we can not use virt-admin to manage other daemons directly. But we can manage it by connecting to the daemon firstly, then executing the monitor/management cmds. Please check the following steps. 

Version-Release number of selected component (if applicable):
libvirt-7.10.0-1.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. try to use virt-admin to check the info about virtqemud
# virt-admin server-threadpool-info virtqemud
error: Server not found: No server named 'virtqemud'

2. try to connect to virtqemud, then check the info about virtqemud
# virt-admin -c virtqemud:///system server-threadpool-info virtqemud
minWorkers     : 5
maxWorkers     : 20
nWorkers       : 5
freeWorkers    : 5
prioWorkers    : 5
jobQueueDepth  : 0

3. change the attributes of virtqemud using the above method
# virt-admin -c virtqemud:///system server-threadpool-set virtqemud --min-workers 10

# virt-admin -c virtqemud:///system server-threadpool-info virtqemud
minWorkers     : 10
maxWorkers     : 20
nWorkers       : 10
freeWorkers    : 10
prioWorkers    : 5
jobQueueDepth  : 0


Actual results:
But the above info has not been added to the docs, e.g., manpages, and https://libvirt.org/manpages/virt-admin.html

Expected results:
Doc about the above info should be added

Additional info:
Comment 1 Peter Krempa 2022-01-21 13:29:21 UTC 
Fixed upstream:

commit 61ad7001299c83b2add18c2ba6d286c04c74ec15
Author: Peter Krempa <pkrempa>
Date:   Thu Jan 20 16:20:22 2022 +0100

    man: virt-admin: Mention monolithic daemon URIs
    
    Hint users that they can use 'virt-admin' also for the new monolithic
    daemons.
    
    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2038045
    Signed-off-by: Peter Krempa <pkrempa>
    Reviewed-by: Erik Skultety <eskultet>

v8.0.0-135-g61ad700129
Comment 2 Lili Zhu 2022-03-19 11:48:03 UTC 
Tested with:
libvirt-daemon-8.2.0-1.fc35.x86_64

check the virt-admin manpages

# man virt-admin

-c, --connect URI

       Connect to the specified URI, as if by the connect command, instead of the default connection. See NOTES


NOTES
       The virt-admin supports both the monolithic libvirtd daemon and the modular daemons whichever is in use by your system. The connection URI used with  -c/--connect  or
       the connect command is based on the name of the controlled daemon e.g.: virtqemud:///system, libvirtd:///system.

       Running virt-admin requires root privileges when communicating with the system instance of a daemon (URI ending in /system) due to the communications channels used to
       talk to the daemon.

connect
....

       See NOTES on picking the correct URI corresponding to a libvirt daemon.
Comment 5 Lili Zhu 2022-04-29 04:01:05 UTC 
Verified this bug with:
libvirt-8.2.0-1.el9.x86_64

The testing steps are the same with Comment #2.

The testing result matches with the expected result, mark the bug as verified.
Comment 7 errata-xmlrpc 2022-11-15 10:03:03 UTC 
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 (Low: libvirt 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:8003
Note You need to log in before you can comment on or make changes to this bug.