From nobody Sun Feb 8 14:30:59 2026 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) client-ip=170.10.129.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1642692944; cv=none; d=zohomail.com; s=zohoarc; b=MmOVQFK0K601pMrpABxBdkLV4easV+8LdMhBP4uBBPS7iB+8DAqMb9FdwRAs1TpIrie1s4PyKTp4bJHn2XsxAKl7eXIczs5ijJ0GFx8u8rD8m8RZ/CJeis57mI3/CQd5vywN8Tlju9nk6TJAowaeNjsDslknc7ejJmfd+88aSKs= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1642692944; h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=vQdtYvp/Skdo1s2csVcjS+pugJRIsAAn5mFDe3wwWsk=; b=nXW1rCQ05PmmaNSLLVoVfJrAQMNA+OoYPo+QPDRO1vcdQs0goH5BaSUZPonHBEVCgCGL+jQliSXG4HIPvKaYrLi3EJF0yX0/FBu8f0O8nFwteV6GqR9w5Kkr7yO+Gu7uTxoxg1PdmWq29kEsKHdmurc1RB8n7o2D4rUp8HcDNtA= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.zohomail.com with SMTPS id 1642692944408941.6762863227574; Thu, 20 Jan 2022 07:35:44 -0800 (PST) Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-297-ZC25WPQXNVSClAptUhXO1A-1; Thu, 20 Jan 2022 10:35:41 -0500 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 476751926DA0; Thu, 20 Jan 2022 15:35:36 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 1ECD810A3943; Thu, 20 Jan 2022 15:35:36 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id D065B4CA9B; Thu, 20 Jan 2022 15:35:35 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 20KFYDlU020600 for ; Thu, 20 Jan 2022 10:34:13 -0500 Received: by smtp.corp.redhat.com (Postfix) id 006C52B45F; Thu, 20 Jan 2022 15:34:13 +0000 (UTC) Received: from speedmetal.redhat.com (unknown [10.40.208.7]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5782D282E9 for ; Thu, 20 Jan 2022 15:34:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1642692943; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=vQdtYvp/Skdo1s2csVcjS+pugJRIsAAn5mFDe3wwWsk=; b=N+YpaSdchxD/hFevkqQPJU1Use7sl3LwaPLGksWjAelpxmkQYX6Vz+y38DOC7RtlPsSaeu hMR8M3hldbeaznK5p+/gAbZQXoptcXs8ZxfxAUiwQ+va03ZJb/Uxc17h0GCww0KftDxR4J 3wBmsy7koCEH/D3ipC/wf4WRoBARWmg= X-MC-Unique: ZC25WPQXNVSClAptUhXO1A-1 From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH v2 2/3] kbase: debuglogs: Fix for modular daemons Date: Thu, 20 Jan 2022 16:34:02 +0100 Message-Id: In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-loop: libvir-list@redhat.com X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1642692945911100001 Content-Type: text/plain; charset="utf-8" Modular daemons are now the default in many new installations, thus we need to include steps how to determine that modular daemons are used and modular-daemon specific locations for the config files and admin URIs. Signed-off-by: Peter Krempa Reviewed-by: Erik Skultety --- docs/kbase/debuglogs.rst | 98 ++++++++++++++++++++++++++++++++-------- 1 file changed, 79 insertions(+), 19 deletions(-) diff --git a/docs/kbase/debuglogs.rst b/docs/kbase/debuglogs.rst index c3d4d3a425..d2632cfff1 100644 --- a/docs/kbase/debuglogs.rst +++ b/docs/kbase/debuglogs.rst @@ -92,38 +92,94 @@ important. Libvirt daemons logging configuration =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +Libvirt daemons can be configured either via a config file or via the +administration API. The configuration location depends on multiple factors. + +Session vs system daemons +------------------------- + +Libvirt daemons run either in the ``system`` mode or on ``session`` (user) +mode, depending on the configuration of the host and available permission +levels. + +The `connection URI `__ influences which dae= mon +the client will communicate with. + +System daemon mode +~~~~~~~~~~~~~~~~~~ + * all connection URIs end in ``/system`` e.g. ``qemu:///system`` + + * config files are usually placed in ``/etc/libvirt`` + +Session daemon mode +~~~~~~~~~~~~~~~~~~~ + + * connection URIs end in ``/session`` + + * config files are usually placed in ``$XDG_CONFIG_HOME/libvirt/`` direc= tory + +Modular vs. monolithic daemons +------------------------------ + +While there is only a single 'libvirtd.conf' configuration file in case of= the +monolithic daemon setup, each of the modular daemons has their own +configuration file giving you a lot of possibilities how to configure them +individually including logging. Realistically though, logging will have to= be +configured only for a single or a couple of daemons in case debug logs are +requested. + + +Refer to `documentation about daemons <../daemons.html#checking-whether-mo= dular-monolithic-mode-is-in-use>`__ +to figure out which is in use by your system. + +Modular daemons +~~~~~~~~~~~~~~~ + +The configuration of modular daemons is in file named after the daemon. E.= g. +for ``qemu:///system`` connection this is the ``virtqemud`` daemon and +correspondingly: + + * ``virtqemud.conf`` config file is used + + * ``virtqemud:///system`` or ``virtqemud:///session`` admin URI is used + +Monolithic daemon +~~~~~~~~~~~~~~~~~ + + * ``libvirtd.conf`` config file is used + + * ``libvirtd:///system`` or ``libvirtd:///session`` admin URI is used + when the modular qemu hypervisor driver ``virtqemud`` + Persistent setting ------------------ -The daemon configuration files location is dependent on `connection -URI `__. For ``qemu:///system``: - +In order to setup libvirt logging persistently, follow the steps below: +- open the appropriate daemon config file in your favourite editor :: -- open ``/etc/libvirt/libvirtd.conf`` in your favourite editor -- find & replace, or set these variables: + /etc/libvirt/virtqemud.conf + /etc/libvirt/libvirtd.conf + $XDG_CONFIG_HOME/libvirt/libvirtd.conf + $XDG_CONFIG_HOME/libvirt/virtqemud.conf -:: +- find & replace, or set the apropriate `Log outputs`_ and `Log filters`_= , e.g :: - log_filters=3D"3:remote 4:event 3:util.json 3:rpc 1:*" - log_outputs=3D"1:file:/var/log/libvirt/libvirtd.log" + log_filters=3D"3:remote 4:event 3:util.json 3:rpc 1:*" + log_outputs=3D"1:file:/var/log/libvirt/libvirtd.log" - save and exit -- restart libvirtd service - -:: +- restart the corresponding service/daemon e.g. :: - systemctl restart libvirtd.service + systemctl restart virtqemud.socket + systemctl restart libvirtd.socket + systemctl restart libvirtd.service *Note:* Libvirt prior to the ``libvirt-4.4.0`` release didn't support glob= bing patterns and thus requires more configuration. See `Legacy (pre-4.4.0) libvirt daemon logging configuration`_. -However, when you are using the session mode ``qemu:///session`` or you ru= n the -``libvirtd`` as unprivileged user you will find configuration file under -``$XDG_CONFIG_HOME/libvirt/libvirtd.conf``. - Runtime setting --------------- @@ -132,9 +188,13 @@ after the daemon restarts, since the new session can m= ake the anomaly "disappear". Therefore, it's possible to enable the debug logs during runt= ime using libvirt administration API. To use it conveniently, there's the ``virt-admin`` client provided by the ``libvirt-admin`` package. Use the -package manager provided by your distribution to install this package. Onc= e you -have it installed, run the following as root to see the set of log filters -currently being active: +package manager provided by your distribution to install this package. + +**Important**: Substitute ``virt-admin -c $ADMIN_URI`` according to the +guideline in the sections above in place of ``virt-admin`` in the examples +below if needed. + +The following command allows to query the list of currently active log fil= ters: :: --=20 2.34.1