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 1457193 - "libvirtd --verbose" doesn't output verbose messages when log_level is 2/3/4
Summary: "libvirtd --verbose" doesn't output verbose messages when log_level is 2/3/4
Keywords:
Status: CLOSED DUPLICATE of bug 1442947
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.4
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Erik Skultety
QA Contact: yafu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-31 09:48 UTC by yafu
Modified: 2017-08-28 14:38 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-28 14:38:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description yafu 2017-05-31 09:48:49 UTC 
Description of problem:
"libvirtd --verbose" doesn't output verbose messages when log_level is 2/3/4

Version-Release number of selected component:
libvirt-3.2.0-6.virtcov.el7.x86_64

How reproducible:
100%

Steps to reproduce:
1.Don't change log setting in /etc/libvirt/virtlog.conf,the default log_level is 3.

2.Stop libvirtd service
# systemctl stop libvirtd


3.# libvirtd --verbose
no output

4.Change log_level 2 or 4, the result is same with step 3.

Actual results:
"libvirtd --verbose" doesn't output verbose messages when log_level is 2/3/4

Expected results:
"libvirtd --verbose" can output verbose messages when log_level is 2/3/4.
Comment 2 yafu 2017-05-31 09:52:20 UTC 
(In reply to yafu from comment #0)
> Description of problem:
> "libvirtd --verbose" doesn't output verbose messages when log_level is 2/3/4
> 
> Version-Release number of selected component:
> libvirt-3.2.0-6.virtcov.el7.x86_64
> 
> How reproducible:
> 100%
> 
> Steps to reproduce:
> 1.Don't change log setting in /etc/libvirt/virtlog.conf,the default
> log_level is 3.
> 
Correct "/etc/libvirt/virtlogd.conf" to "/etc/libvirt/libvirtd.conf"

> 2.Stop libvirtd service
> # systemctl stop libvirtd
> 
> 
> 3.# libvirtd --verbose
> no output
> 
> 4.Change log_level 2 or 4, the result is same with step 3.
> 
> Actual results:
> "libvirtd --verbose" doesn't output verbose messages when log_level is 2/3/4
> 
> Expected results:
> "libvirtd --verbose" can output verbose messages when log_level is 2/3/4.
Comment 3 Jaroslav Suchanek 2017-06-02 10:11:42 UTC 
I suspect this commit:
commit 94c465d0eb5cc3c0f6908a6b11fad83887ec0216
Author:     Erik Skultety <eskultet>
AuthorDate: Mon Oct 31 12:52:51 2016 +0100
Commit:     Erik Skultety <eskultet>
CommitDate: Thu Dec 15 10:36:23 2016 +0100

    daemon: Hook up the virLog{Get,Set}DefaultOutput to the daemon's init routine
    
    Now that virLog{Get,Set}DefaultOutput routines are introduced we can wire them
    up to the daemon's logging initialization code. Also, change the order of
    operations a bit so that we still strictly honor our precedence of settings:
    cmdline > env > config now that outputs and filters are not appended anymore.
    
    Signed-off-by: Erik Skultety <eskultet>
Comment 4 Erik Skultety 2017-08-28 14:38:13 UTC 

*** This bug has been marked as a duplicate of bug 1442947 ***
Note You need to log in before you can comment on or make changes to this bug.