From nobody Sun Feb 8 18:31:09 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=1650630230; cv=none; d=zohomail.com; s=zohoarc; b=EpcCLQ9L6j/uxwgIjNV4MhdJwNQJmcQ1jiUXQ8L0NU6wGGBUxpS8QQfR4BhNuhm4+yG4ZNxCflGdWtMND10uta9AbnHOBdL7DqBsqy8T3PxcuNHlZKmhGczsJiO9Mr2Rw5m9xoLKsedLOHGPamHGifDw5X5bBT8HZUwX69M+1aI= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1650630230; 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=Url0FCoPRYpc+hBr616YW5prdQqy6Gbzj0pbIzC1Xiw=; b=eEqWW0xBwjEpGvDmlarN68pm2aLkFzVXJ9noVGFD5qXtgEPTPmbZmOMeB+xKzgZVlC8eJ02GyGCQymIwRXWwT9yUDIhStHZ8YoAgWFue0Zb6bmxdC+okBjf2RBHHiaHGICMo22Bq+0z21bfCcauE2gyNdGRcS3CF+MRKeZdd4WM= 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 1650630230816395.867006020655; Fri, 22 Apr 2022 05:23:50 -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-207-wDpvDSNhOa-lvpoXYkGdwA-1; Fri, 22 Apr 2022 08:23:46 -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 C663B1014A67; Fri, 22 Apr 2022 12:23:41 +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 AA97154CE4D; Fri, 22 Apr 2022 12:23:41 +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 78A321940351; Fri, 22 Apr 2022 12:23:41 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id EE918194034C for ; Fri, 22 Apr 2022 12:23:40 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id E1713572328; Fri, 22 Apr 2022 12:23:40 +0000 (UTC) Received: from speedmetal.lan (unknown [10.40.208.36]) by smtp.corp.redhat.com (Postfix) with ESMTP id 48D47416361 for ; Fri, 22 Apr 2022 12:23:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1650630229; 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=Url0FCoPRYpc+hBr616YW5prdQqy6Gbzj0pbIzC1Xiw=; b=DATIK9Uzswc3UrN0XAtu7jRCny+ThpbNblMj6S8g/WjNSWIl0KslNBBMjemlnDBgYlP0Wy 48bTBJ0jKPdYmj8yDwgVz3nrUeSY7+Gg9q26kU1IydWlQKTxuhVTq+36hOXoCETQXRulMK Maxua45bLv9LviIA16BwiFEuo7hhrz4= X-MC-Unique: wDpvDSNhOa-lvpoXYkGdwA-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 08/15] docs: uri: Remove old 'NULL URI' section Date: Fri, 22 Apr 2022 14:23:24 +0200 Message-Id: In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.85 on 10.11.54.10 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-type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1650630231938100009 We now have an paragraph about default URI choice if the passed pointer is NULL. Add the two related bits from the 'NULL and empty string URIs' from the legacy section to the current one and remove the old stuff. Signed-off-by: Peter Krempa --- docs/uri.rst | 25 ++++--------------------- 1 file changed, 4 insertions(+), 21 deletions(-) diff --git a/docs/uri.rst b/docs/uri.rst index 949032e0ff..80c2d780c3 100644 --- a/docs/uri.rst +++ b/docs/uri.rst @@ -51,13 +51,15 @@ outside the allowed alias character set, no alias looku= p will be attempted. Default URI choice ------------------ -If the URI passed to ``virConnectOpen*`` is NULL, then libvirt will use the -following logic to determine what URI to use. +If the URI passed to ``virConnectOpen*`` is NULL or empty string, then lib= virt +will use the following logic to determine what URI to use. #. The environment variable ``LIBVIRT_DEFAULT_URI`` #. The client configuration file ``uri_default`` parameter #. Probe each hypervisor in turn until one that works is found +Historically an empty URI was equivalent to ``xen:///system``. + Specifying URIs to virsh, virt-manager and virt-install ------------------------------------------------------- @@ -420,25 +422,6 @@ The test driver is a dummy hypervisor for test purpose= s. The URIs supported are: Other & legacy URI formats -------------------------- -NULL and empty string URIs -~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Libvirt allows you to pass a ``NULL`` pointer to ``virConnectOpen*``. Empty -string (``""``) acts in the same way. Traditionally this has meant =E2=80= =9Cconnect to -the local Xen hypervisor=E2=80=9D. However in future this may change to me= an =E2=80=9Cconnect to -the best available hypervisor=E2=80=9D. - -The theory is that if, for example, Xen is unavailable but the machine is -running an OpenVZ kernel, then we should not try to connect to the Xen -hypervisor since that is obviously the wrong thing to do. - -In any case applications linked to libvirt can continue to pass ``NULL`` a= s a -default choice, but should always allow the user to override the URI, eith= er by -constructing one or by allowing the user to type a URI in directly (if tha= t is -appropriate). If your application wishes to connect specifically to a Xen -hypervisor, then for future proofing it should choose a full -`xen:///system URI`_. - Legacy: ``"xen"`` ~~~~~~~~~~~~~~~~~ --=20 2.35.1