From nobody Mon Feb 9 01:47:22 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=1654009873; cv=none; d=zohomail.com; s=zohoarc; b=dv/q3KhI0WJqSOR10N7MwrpJK7SJEi+69KBG9Qh9L9jKoN8bhTdvrZZrN2t/i7wI4FAdIgdo1QNnrC28x2p9wAEtjW49GfHs6lJHs/2YQ3Liz39z99x6sucdjc31nmdVBRp08gvZbQC86G82gu1GaSJKLkO+IriXUBTrc4aRUYU= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1654009873; 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=HibVxaQ3Ahi2uEun93Pv5pxRljMrgydRtQhap7FiM3w=; b=UHEiW13+GkWYnQsHAZzdIqsNkRWbZQbltFac5uwHuRPEnKpsb2CInl54e5/aSPuXZ/EGe0DKtOin6zfVTflP+75OcWeFYWxxQmZLhuxBcHSPah8WXO3gj1kBTVEjQVeR5c3gm3K34ZgAF6BfWU+3tCN9kw45GBSgbOBEjrrDhuY= 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 1654009873438396.3273116243064; Tue, 31 May 2022 08:11:13 -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-250-h-Ba5BsrPnGRGKHooVJkmA-1; Tue, 31 May 2022 11:08:40 -0400 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 68103857D56; Tue, 31 May 2022 15:07:32 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (unknown [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id 4EA8B492CA2; Tue, 31 May 2022 15:07:32 +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 BEA2319451EC; Tue, 31 May 2022 15:07:31 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 6405D1947065 for ; Tue, 31 May 2022 15:07:30 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 4ADBA8287E; Tue, 31 May 2022 15:07:30 +0000 (UTC) Received: from speedmetal.lan (unknown [10.40.208.21]) by smtp.corp.redhat.com (Postfix) with ESMTP id CB78810725 for ; Tue, 31 May 2022 15:07:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1654009870; 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=HibVxaQ3Ahi2uEun93Pv5pxRljMrgydRtQhap7FiM3w=; b=b5j76Fc/kvetrBlAoQH9TV9jQYXpBUlwefCFnsRAOSVESk4LZ2iEvHb0YH3lgrSUoH1pn5 CB0xZK6nrfqYxUZEvzIIocVytKgDhM7PmdeNsCQvHUbarATgEBRUzIuU7ExAB8cMM+IVTq T11mTuR6iQO0kBRp+MrLC2vtuJPKGeQ= X-MC-Unique: h-Ba5BsrPnGRGKHooVJkmA-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 55/67] docs: domainstatecapture: Fix broken links Date: Tue, 31 May 2022 17:06:30 +0200 Message-Id: In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 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.85 on 10.11.54.9 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: 1654009874327100001 Content-Type: text/plain; charset="utf-8" Some links didn't exit the 'kbase/' directory and 'virDomainBackupEnd' API never existed. Signed-off-by: Peter Krempa Reviewed-by: J=C3=A1n Tomko --- docs/kbase/domainstatecapture.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/kbase/domainstatecapture.rst b/docs/kbase/domainstatecapt= ure.rst index cefc381d2e..204e74c18f 100644 --- a/docs/kbase/domainstatecapture.rst +++ b/docs/kbase/domainstatecapture.rst @@ -176,12 +176,12 @@ capture have these properties: contents are not also saved. Since creating an external snapshot changes which disk image resource is in use by the guest, this API can be coupled with - `virDomainBlockCommit() `__ + `virDomainBlockCommit() <../html/libvirt-libvirt-domain.html#virDomainB= lockCommit>`__ to restore things back to the guest using its original disk image, where a third-party tool can read the backing file prior to the live - commit. See also the `XML details `__ used with + commit. See also the `XML details <../formatsnapshot.html>`__ used with this command. -`virDomainFSFreeze `__= , `virDomainFSThaw `__ +`virDomainFSFreeze <../html/libvirt-libvirt-domain.html#virDomainFSFreeze>= `__, `virDomainFSThaw <../html/libvirt-libvirt-domain.html#virDomainFSThaw>= `__ This pair of APIs does not directly capture guest state, but can be used to coordinate with a trusted live guest that state capture is about to happen, and therefore guest I/O should be quiesced so that @@ -191,7 +191,7 @@ capture have these properties: to these functions. Also, note that freezing guest I/O is only possible with trusted guests running a guest agent, and that some guests place maximum time limits on how long I/O can be frozen. -`virDomainCheckpointCreateXML `__ +`virDomainCheckpointCreateXML <../html/libvirt-libvirt-domain-checkpoint.h= tml#virDomainCheckpointCreateXML>`__ This API does not actually capture guest state, rather it makes it possible to track which portions of guest disks have changed between a checkpoint and the current live execution of the guest. However, @@ -201,9 +201,9 @@ capture have these properties: at the creation of an external snapshot with ``virDomainSnapshotCreateXML2()``, since a second incremental backup is most useful when using the checkpoint created during the first. - See also the `XML details `__ used with this + See also the `XML details <../formatcheckpoint.html>`__ used with this command. -`virDomainBackupBegin `__, `virDomainBackupEnd `__ +`virDomainBackupBegin <../html/libvirt-libvirt-domain.html#virDomainBackup= Begin>`__ This API wraps approaches for capturing the state of disks of a running guest, but does not track accompanying guest memory state. The capture is consistent to the start of the operation, where the --=20 2.35.3