From nobody Wed May 14 20:32:27 2025 Delivered-To: importer@patchew.org Received-SPF: pass (zoho.com: domain of redhat.com designates 209.132.183.28 as permitted sender) client-ip=209.132.183.28; envelope-from=libvir-list-bounces@redhat.com; helo=mx1.redhat.com; Authentication-Results: mx.zohomail.com; spf=pass (zoho.com: domain of redhat.com designates 209.132.183.28 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mx.zohomail.com with SMTPS id 1522292468656484.44657249003774; Wed, 28 Mar 2018 20:01:08 -0700 (PDT) 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 mx1.redhat.com (Postfix) with ESMTPS id C583A19CF76; Thu, 29 Mar 2018 03:01:06 +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 992885C2E1; Thu, 29 Mar 2018 03:01:06 +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 2FD1E180BAD3; Thu, 29 Mar 2018 03:01:06 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id w2T30fNK007432 for ; Wed, 28 Mar 2018 23:00:41 -0400 Received: by smtp.corp.redhat.com (Postfix) id 957375D9C5; Thu, 29 Mar 2018 03:00:41 +0000 (UTC) Received: from mx1.redhat.com (ext-mx01.extmail.prod.ext.phx2.redhat.com [10.5.110.25]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 8D0985D726 for ; Thu, 29 Mar 2018 03:00:40 +0000 (UTC) Received: from smtp2.provo.novell.com (smtp2.provo.novell.com [137.65.250.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 02C677F3EC for ; Thu, 29 Mar 2018 03:00:39 +0000 (UTC) Received: from linux-tbji.provo.novell.com (prv-ext-foundry1int.gns.novell.com [137.65.251.240]) by smtp2.provo.novell.com with ESMTP (NOT encrypted); Wed, 28 Mar 2018 21:00:34 -0600 From: Jim Fehlig To: libvir-list@redhat.com Date: Wed, 28 Mar 2018 20:58:31 -0600 Message-Id: <20180329025832.22875-7-jfehlig@suse.com> In-Reply-To: <20180329025832.22875-1-jfehlig@suse.com> References: <20180329025832.22875-1-jfehlig@suse.com> X-Greylist: Sender passed SPF test, Sender IP whitelisted by DNSRBL, ACL 207 matched, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Thu, 29 Mar 2018 03:00:39 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Thu, 29 Mar 2018 03:00:39 +0000 (UTC) for IP:'137.65.250.81' DOMAIN:'smtp2.provo.novell.com' HELO:'smtp2.provo.novell.com' FROM:'jfehlig@suse.com' RCPT:'' X-RedHat-Spam-Score: -2.301 (RCVD_IN_DNSWL_MED, SPF_PASS) 137.65.250.81 smtp2.provo.novell.com 137.65.250.81 smtp2.provo.novell.com X-Scanned-By: MIMEDefang 2.83 on 10.5.110.25 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-loop: libvir-list@redhat.com Subject: [libvirt] [PATCH 6/7] docs: remove mention of legacy Xen driver 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: , MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Thu, 29 Mar 2018 03:01:07 +0000 (UTC) X-ZohoMail: RSF_0 Z_629925259 SPT_0 Content-Type: text/plain; charset="utf-8" Signed-off-by: Jim Fehlig --- docs/architecture.html.in | 28 ++++-------------- docs/bugs.html.in | 3 +- docs/uri.html.in | 74 -------------------------------------------= ---- docs/windows.html.in | 2 +- 4 files changed, 9 insertions(+), 98 deletions(-) diff --git a/docs/architecture.html.in b/docs/architecture.html.in index f1461ba88..cab4880a5 100644 --- a/docs/architecture.html.in +++ b/docs/architecture.html.in @@ -19,32 +19,16 @@ in "Domain 0", which is the primary Linux OS loaded on the machine. That OS kernel provides most if not all of the actual drivers used by the set of domains. It also runs the Xen Store, a database of information shared by t= he -hypervisor, the kernels, the drivers and the xen daemon. Xend. The xen dae= mon -supervise the control and execution of the sets of domains. The hypervisor, +hypervisor, the backend drivers, any running domains, and libxl (aka libxe= nlight). +libxl provides a set of APIs for creating and managing domains, which can = be used +by applications such as the xl tool provided by Xen or libvirt. The hyperv= isor, drivers, kernels and daemons communicate though a shared system bus implemented in the hypervisor. The figure below tries to provide a view of this environment:

3D"The -

The library can be initialized in 2 ways depending on the level of -privilege of the embedding program. If it runs with root access, -virConnectOpen() can be used, it will use three different ways to connect = to -the Xen infrastructure:

-
    -
  • a connection to the Xen Daemon though an HTTP RPC layer
    • -
  • a read/write connection to the Xen Store
    • -
  • use Xen Hypervisor calls
    • -
  • when used as non-root libvirt connect to a proxy daemon running - as root and providing read-only support
    • -
-

The library will usually interact with the Xen daemon for any opera= tion -changing the state of the system, but for performance and accuracy reasons -may talk directly to the hypervisor when gathering state information at -least when possible (i.e. when the running program using libvirt has root -privilege access).

-

If it runs without root access virConnectOpenReadOnly() should be u= sed to -connect to initialize the library. It will then fork a libvirt_proxy -program running as root and providing read_only access to the API, this is -then only useful for reporting and monitoring.

+

The library will interact with libxl for all management operations +on a Xen system.

+

Not that the libvirt libxl driver only supports root access.

=20

QEmu and KVM support

=20 diff --git a/docs/bugs.html.in b/docs/bugs.html.in index 12a1090c1..553422338 100644 --- a/docs/bugs.html.in +++ b/docs/bugs.html.in @@ -122,7 +122,8 @@
  • The hardware architecture being used
  • The name of the hypervisor (Xen, QEMU, KVM)
  • The XML config of the guest domain if relevant
    • -
  • For Xen hypervisor, the XenD logfile from /var/log/xen
    • +
  • For Xen hypervisor, the domain logfiles from /var/log/xen and + /var/log/libvirt/libxl
  • For QEMU/KVM, the domain logfile from /var/log/libvirt/qemu
    • =20 diff --git a/docs/uri.html.in b/docs/uri.html.in index ade726089..5df73613a 100644 --- a/docs/uri.html.in +++ b/docs/uri.html.in @@ -253,59 +253,6 @@ the user to type a URI in directly (if that is appropr= iate). If your application wishes to connect specifically to a Xen hypervisor, then for future proofing it should choose a full xen= :/// URI.

    -

    - File paths (xend-unix-server) -

    -

    -If XenD is running and configured in /etc/xen/xend-config.sxp: -

    - 
    -(xend-unix-server yes)
-
    -

    -then it listens on a Unix domain socket, usually at -/var/lib/xend/xend-socket. You may pass a different path -using a file URI such as: -

    - 
    -virsh -c ///var/run/xend/xend-socket
-
    -

    - Legacy: http://... (xend-http-server= ) -

    -

    -If XenD is running and configured in /etc/xen/xend-config.sxp: - -

    - 
    -(xend-http-server yes)
-
    -

    -then it listens on TCP port 8000. libvirt allows you to -try to connect to xend running on remote machines by passing -http://hostname[:port]/, for example: - -

    - 
    -virsh -c http://oirase/ list
-
    -

    -This method is unencrypted and insecure and is definitely not -recommended for production use. Instead use libvi= rt's remote support. -

    -

    -Notes: -

    -
      -
    1. The HTTP client does not fully support IPv6.
      2. -
    2. Many features do not work as expected across HTTP connections, = in - particular, virConnectGetCapabilities. - The remote support however does work - correctly.
      3. -
    3. XenD's new-style XMLRPC interface is not supported by - libvirt, only the old-style sexpr interface known in the Xen - documentation as "unix server" or "http server".
      4. -

    Legacy: "xen"

    @@ -313,27 +260,6 @@ Notes: Another legacy URI is to specify name as the string "xen". This will continue to refer to the Xen hypervisor. However you should prefer a full x= en:/// URI in all future code. -

    -

    - Legacy: Xen proxy -

    -

    -Libvirt continues to support connections to a separately running Xen -proxy daemon. This provides a way to allow non-root users to make a -safe (read-only) subset of queries to the hypervisor. -

    -

    -There is no specific "Xen proxy" URI. However if a Xen URI of any of -the ordinary or legacy forms is used (eg. NULL, -"", "xen", ...) which fails, and the -user is not root, and the Xen proxy socket can be connected to -(/tmp/libvirt_proxy_conn), then libvirt will use a proxy -connection. -

    -

    -You should consider using libvirt remote support -in future. Since 0.8.6 libvirt doesn't contain -the Xen proxy anymore and you should use libvirtd instead.

    diff --git a/docs/windows.html.in b/docs/windows.html.in index 3f012d18d..57abf8fde 100644 --- a/docs/windows.html.in +++ b/docs/windows.html.in @@ -185,7 +185,7 @@ --without-avahi \ --without-polkit \ --without-python \ - --without-xen \ + --without-libxl \ --without-qemu \ --without-lxc \ --without-openvz \ --=20 2.16.2 -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list