From nobody Sun Feb 8 23: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=1642692863; cv=none; d=zohomail.com; s=zohoarc; b=RSqr4qXicLNEuwOk7gA5FhdfYvlShnjkUn19yBmFw/MxfcGBJkZW0fbvdAA6lwKWLBy0Pul6HsT3ZNHtTG8sOoZLv97/0Vl3USSQb5ulo1n7bKW68oPCFe2MiVrAN0ISWiXgF0tu3pS13WzTPqA0WptKet/KnBzmfbOCnRhQ1Nw= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1642692863; 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=22sNTrHjiftNFYGqjt9ObL/BXc+mTFfsZzQqpKX8zeU=; b=Nkb89t9wQa9xg721+uZCYvBSGwylD+ThJOKHAXINfmKsE9l7ouWnF3G8KrpgJrXELvY3gPnDYZCxtlrSXenRAsRsNwpP8r0Nfni/4mNw26NL5xr8co27h4L8rtytkjHRkQ+A5IMrasK7TH6qeTFWqQP/Ab6G8gfbyWZRmffVJEs= 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 1642692863435702.4314687535613; Thu, 20 Jan 2022 07:34:23 -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-228-QSOrDufvNOibvSbJumRr4Q-1; Thu, 20 Jan 2022 10:34:18 -0500 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id AC05851089; Thu, 20 Jan 2022 15:34:13 +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 896377EBC9; Thu, 20 Jan 2022 15:34:13 +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 55E0E4A7C8; Thu, 20 Jan 2022 15:34:13 +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 20KFYBXF020593 for ; Thu, 20 Jan 2022 10:34:11 -0500 Received: by smtp.corp.redhat.com (Postfix) id E57FB282E9; Thu, 20 Jan 2022 15:34:11 +0000 (UTC) Received: from speedmetal.redhat.com (unknown [10.40.208.7]) by smtp.corp.redhat.com (Postfix) with ESMTP id 4E6F32BCFF for ; Thu, 20 Jan 2022 15:34:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1642692862; 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=22sNTrHjiftNFYGqjt9ObL/BXc+mTFfsZzQqpKX8zeU=; b=giyXyUfM3tGPh8FQKxpKVlrtUbI868jPTBu98IzXGlgNOPuW9h0ziGGFg0NrvJuqQECUde 9sKjBhDjPKp8wgk3XJ+5y4wyQpb2/jIhMbQVmHGw6VKSVXXaVkS+FVbkIkZhT9Weg2AdCK 40qTlx5pofv3I/0W9TgJ3Iut6iWWgLw= X-MC-Unique: QSOrDufvNOibvSbJumRr4Q-1 From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH v2 1/3] docs: daemons: Add section on figuring out whether modular or monolithic daemon is in use Date: Thu, 20 Jan 2022 16:34:01 +0100 Message-Id: <21b46e39ed85bb1d11070780be8a103cca7baae9.1642692813.git.pkrempa@redhat.com> 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.79 on 10.5.11.12 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: 1642692865522100001 Content-Type: text/plain; charset="utf-8" Since we are at a transition period where some users may be running monolithic libvirtd and others already the modular topology we need a section that allows users to figure out which is in use. This will be particularly important in the document about enabling logging, as the active log file depends on which daemon is in use. Signed-off-by: Peter Krempa Reviewed-by: Erik Skultety --- docs/daemons.rst | 52 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 52 insertions(+) diff --git a/docs/daemons.rst b/docs/daemons.rst index 1f9bc34260..c3970eb89c 100644 --- a/docs/daemons.rst +++ b/docs/daemons.rst @@ -435,6 +435,58 @@ host first. $ systemctl enable virtproxyd-tls.socket $ systemctl start virtproxyd-tls.socket +Checking whether modular/monolithic mode is in use +=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D + +New distributions are likely to use the modular mode although the upgrade +process preserves whichever mode was in use before the upgrade. + +To determine whether modular or monolithic mode is in use on a host running +``systemd`` as the init system you can take the following steps: + +#. Check whether the modular daemon infrastructure is in use + + First check whether the modular daemon you are interested (see + `Modular driver daemons`_ for a summary of which daemons are provided by + libvirt) in is running: + + #. Check ``.socket`` for socket activated services + + :: + + # systemctl is-active virtqemud.socket + active + + #. Check ``.service`` for always-running daemons + + :: + + # systemctl is-active virtqemud.service + active + + If either of the above is ``active`` your system is using the modular d= aemons. + +#. Check whether the monolithic daemon is in use + + #. Check ``libvirtd.socket`` + + :: + + # systemctl is-active libvirtd.socket + active + + #. Check ``libvirtd.service`` for always-running daemon + + :: + + # systemctl is-active libvirtd.service + active + + If either of the above is ``active`` your system is using the monolithic + daemon. + +#. To determine which of the above will be in use on the next boot of the = system, + substitute ``is-enabled`` for ``is-active`` in the above examples. Proxy daemon =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --=20 2.34.1