From nobody Mon Feb 9 06:27:11 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=1642434058; cv=none; d=zohomail.com; s=zohoarc; b=UIctmaKMBSnd7gPvWu5/T6Dol4rUdAqsMKmxN3D/hG1aHS5aWKu1DdAkhFnqpky3tX95Fnw4YJU2O1D35xAaQq1q60nIatGp5pLKS6upx/ep56ULVh7WZCXu3kIMw/OAWvE14s4NojWzJG6xDK2KnbwhXC9R0HjC+1NtrsSu2gw= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1642434058; 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=Pwg/vuyA74IRFpytlr0xkcPxx8TE0htWl+KhwHlP+N0=; b=l1GzMypyJs7Imbn1LnJdIu16lKXoge8g4sxsEuVM5S0/8XRgVa1Zmd27/p3Tkzn3BoI5SHllgVyv3vT2Ia9HT6FQjJLc2NkynejjB68ejyZyj6Q/UMLAK9pMdEbh6bLvOQwX7kEw070b3x18mVHHJg3iLqfhJJmgQUW/fb/79sg= 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 1642434058554227.910517967058; Mon, 17 Jan 2022 07:40:58 -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-567-ZM978xOvMP-B8kroPdkpZQ-1; Mon, 17 Jan 2022 10:40:42 -0500 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 45DC3835BD1; Mon, 17 Jan 2022 15:39:46 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 27530798DB; Mon, 17 Jan 2022 15:39:46 +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 E70AB1806D1D; Mon, 17 Jan 2022 15:39:44 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 20HFdUjo000478 for ; Mon, 17 Jan 2022 10:39:30 -0500 Received: by smtp.corp.redhat.com (Postfix) id 76F355B920; Mon, 17 Jan 2022 15:39:30 +0000 (UTC) Received: from speedmetal.redhat.com (unknown [10.40.208.7]) by smtp.corp.redhat.com (Postfix) with ESMTP id CFB945444C for ; Mon, 17 Jan 2022 15:39:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1642434057; 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=Pwg/vuyA74IRFpytlr0xkcPxx8TE0htWl+KhwHlP+N0=; b=AXhfd6IgLCDeLSqturmpQzr+yVJlmshVe9Zct3xCYpi79/Fe75AADVwiz0DhpQsbh7VGD2 Gw46IpvVqi/2hrbji835LZ+MvFR976PXPso0fp0/zHrSEpDVpu2Ckb/uDaq0o+gA3QS7/e T0oBSLfQkpwBayCu0hHxo3onkJ0YhUw= X-MC-Unique: ZM978xOvMP-B8kroPdkpZQ-1 From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 2/8] kbase: debuglogs: Use common heading hierarchy Date: Mon, 17 Jan 2022 16:39:10 +0100 Message-Id: <27159d0ac5790b2c116dd4c75d6b014f1712f7ed.1642433476.git.pkrempa@redhat.com> In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 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.79 on 10.5.11.14 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: 1642434060870100001 Content-Type: text/plain; charset="utf-8" Use the heading hierarchy as generated by pandoc which we use in most of the converted XML format docs. Signed-off-by: Peter Krempa --- docs/kbase/debuglogs.rst | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/kbase/debuglogs.rst b/docs/kbase/debuglogs.rst index 3fb06bedc3..967ec10f4a 100644 --- a/docs/kbase/debuglogs.rst +++ b/docs/kbase/debuglogs.rst @@ -5,7 +5,7 @@ Debug Logs .. contents:: Turning on debug logs ---------------------- +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D If you `report a bug `__ against libvirt, in most cases you will be asked to attach debug logs. The= se @@ -18,10 +18,10 @@ well. How to turn on debug logs for libvirt -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +------------------------------------- Persistent setting -^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~ The daemon configuration files location is dependent on `connection URI `__. For ``qemu:///system``: @@ -71,7 +71,7 @@ However, when you are using the session mode ``qemu:///se= ssion`` or you run the ``$XDG_CONFIG_HOME/libvirt/libvirtd.conf``. Runtime setting -^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~ Debugging anomalies can be very painful, especially when trying to reprodu= ce it after the daemon restarts, since the new session can make the anomaly @@ -112,7 +112,7 @@ once you're finished debugging, just remember to save t= he original sets of filters and outputs and restore them at the end the same way as described = above. Removing filters and outputs -'''''''''''''''''''''''''''' +^^^^^^^^^^^^^^^^^^^^^^^^^^^^ It's also possible to remove all the filters and produce an enormous log f= ile, but it is not recommended since some of libvirt's modules can produce a la= rge @@ -136,7 +136,7 @@ setting which depends on the host configuration, *journ= ald* in our case: Logging outputs: 2:journald What to attach? ---------------- +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Now you should go and reproduce the bug. Once you're finished, attach: @@ -156,7 +156,7 @@ Now you should go and reproduce the bug. Once you're fi= nished, attach: required. Example filter settings ------------------------ +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Some filter setting suggestions for debugging more specific things. Unless= it's explicitly stated, these work on libvirt 4.4.0 and later. Please note that= some @@ -164,7 +164,7 @@ of the filters below may not log enough information for= filing a proper libvirt bug. Usually it's better to log more than less. Targeted logging for debugging QEMU VMs -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +--------------------------------------- Specifying only some sections allows for a targeted filter configuration w= hich works on all versions and is sufficient for most cases. @@ -174,7 +174,7 @@ works on all versions and is sufficient for most cases. 1:libvirt 1:qemu 1:conf 1:security 3:event 3:json 3:file 3:object 1:ut= il Less verbose logging for QEMU VMs -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +--------------------------------- Some subsystems are very noisy and usually not the culprit of the problems= . They can be silenced individually for a less verbose log while still logging @@ -186,7 +186,7 @@ A permissive filter is good for development use cases. 3:remote 4:event 3:util.json 3:util.object 3:util.dbus 3:util.netlink = 3:node_device 3:rpc 3:access 1:* Minimalistic QEMU QMP monitor logging -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +------------------------------------- This filter logs only QMP traffic and skips most of libvirt's messages. --=20 2.34.1