From nobody Mon Feb 9 11:05:52 2026 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) client-ip=170.10.133.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.133.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=1648469643; cv=none; d=zohomail.com; s=zohoarc; b=ZMAzGKWu3kREPAfWg21b9G98Lm+moWWTNRaQzgX6+Pl4kQOTVcuBTvaoxdiTfIYxdz15vEA5ATkxRSwI4kzFMhJNnR1qmAkKeT13Fb6HOAjhB5Xz9/hzn6EpmwV/0HI+i2JdNcO6fJTk8GVAsPZ1MS6y7gWHwbG87V4qSzCiJQk= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1648469643; 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=hOeZOoDRYAdmbH5oQwDXzWK+iMWJpLi8UwEaHL8G9AU=; b=b41BM8IYmXhEptpkY28ZZkjV2qNGR6pvMBXv96j7RMZVQ2/PCrFLuGXlsKBrNHvWZOauvJn2K2XDi6rH4RpjkwyMBp5s0ilPU9c6xMCq2MEwWHjdc/eSQlC9aNriy+PHnJJdIfSyu3lLXnPmfXKwLFJ2jYR/D8ibpa97hsifltQ= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.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.133.124]) by mx.zohomail.com with SMTPS id 1648469643229731.1428222918655; Mon, 28 Mar 2022 05:14:03 -0700 (PDT) Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-408-m7-lXt53NXSjadMqCkcc3A-1; Mon, 28 Mar 2022 08:11:23 -0400 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id BA70718A6582; Mon, 28 Mar 2022 12:11:20 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id A1EB22024CBA; Mon, 28 Mar 2022 12:11:20 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 6C9881947BBE; Mon, 28 Mar 2022 12:11:20 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 69A851940376 for ; Mon, 28 Mar 2022 12:11:14 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 460AB141DC29; Mon, 28 Mar 2022 12:11:14 +0000 (UTC) Received: from speedmetal.lan (unknown [10.40.208.35]) by smtp.corp.redhat.com (Postfix) with ESMTP id BA6FB1410F3B for ; Mon, 28 Mar 2022 12:11:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1648469642; 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=hOeZOoDRYAdmbH5oQwDXzWK+iMWJpLi8UwEaHL8G9AU=; b=i1MCirEsPsIimhrlMhWK9Kv1T06qSpTVNO2tnEtsaxxyj/mT7YfKvLXhVHE8tKTTSGe7XG U3V+gXFAYCKeXZLRzunclfQgy38W9JGn8CNcaF8TO6lrRDf6wbRtL5kVRQWUWY6Pp2Qlyq Q1+1nrClou9RlJazTSM/o+vRXzj+394= X-MC-Unique: m7-lXt53NXSjadMqCkcc3A-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 28/29] docs: logging: Replace example by link to kbase/debuglogs.html Date: Mon, 28 Mar 2022 14:10:43 +0200 Message-Id: <909e61269f2832eb5c4023d7ff55e0e0cf4bb4c7.1648469356.git.pkrempa@redhat.com> In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.85 on 10.11.54.7 X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libvir-list-bounces@redhat.com Sender: "libvir-list" X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 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: 1648469643771100001 Content-Type: text/plain; charset="utf-8"; x-default="true" The 'debuglogs' knowledge base page has way more info and examples on how to set logging use it instead of the ad-hoc examples. Signed-off-by: Peter Krempa Reviewed-by: Erik Skultety --- docs/logging.rst | 34 +++------------------------------- 1 file changed, 3 insertions(+), 31 deletions(-) diff --git a/docs/logging.rst b/docs/logging.rst index 204176c6f5..c7c14504ae 100644 --- a/docs/logging.rst +++ b/docs/logging.rst @@ -210,34 +210,6 @@ specific message ID values Examples -------- -For example setting up the following: - -:: - - export LIBVIRT_DEBUG=3D1 - export LIBVIRT_LOG_OUTPUTS=3D"1:file:virsh.log" - -and then running virsh will accumulate the logs in the ``virsh.log`` file = in a -way similar to: - -:: - - 14:29:04.771: debug : virInitialize:278 : register drivers - 14:29:04.771: debug : virRegisterDriver:618 : registering Test as drive= r 0 - -the messages are timestamped, there is also the level recorded, if debug t= he -name of the function is also printed and then the formatted message. This = should -be sufficient to at least get a precise idea of what is happening and where -things are going wrong, allowing to then put the correct breakpoints when -running under a debugger. - -To activate full debug of the libvirt entry points, utility functions and = the -QEMU/KVM driver, set: - -:: - - log_filters=3D"1:libvirt 1:util 1:qemu" - log_outputs=3D"1:file:/var/log/libvirt/libvirtd.log" - -in libvirtd.conf and restart the daemon will allow to gather a copious amo= unt of -debugging traces for the operations done in those areas. +Examples with useful log settings along with more information on how to pr= operly +configure logging for various situations can be found in the +`logging knowledge base article `__. --=20 2.35.1