From nobody Wed May 14 20:23:17 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 1523047542457877.5465248860429; Fri, 6 Apr 2018 13:45:42 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 56DA378547; Fri, 6 Apr 2018 20:45:40 +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 1EE8E9E377; Fri, 6 Apr 2018 20:45:40 +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 B858B4CA9C; Fri, 6 Apr 2018 20:45:38 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id w36KjbC0026098 for ; Fri, 6 Apr 2018 16:45:37 -0400 Received: by smtp.corp.redhat.com (Postfix) id BAEEB18A29; Fri, 6 Apr 2018 20:45:37 +0000 (UTC) Received: from mx1.redhat.com (ext-mx10.extmail.prod.ext.phx2.redhat.com [10.5.110.39]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B5D7D620AA for ; Fri, 6 Apr 2018 20:45:37 +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 E331E62E8A for ; Fri, 6 Apr 2018 20:45:35 +0000 (UTC) Received: from linux-tbji.gns.novell.com (prv-ext-foundry1int.gns.novell.com [137.65.251.240]) by smtp2.provo.novell.com with ESMTP (NOT encrypted); Fri, 06 Apr 2018 14:45:30 -0600 From: Jim Fehlig To: libvir-list@redhat.com Date: Fri, 6 Apr 2018 14:45:00 -0600 Message-Id: <20180406204500.616-9-jfehlig@suse.com> In-Reply-To: <20180406204500.616-1-jfehlig@suse.com> References: <20180406204500.616-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.39]); Fri, 06 Apr 2018 20:45:36 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Fri, 06 Apr 2018 20:45:36 +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.78 on 10.5.110.39 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-loop: libvir-list@redhat.com Subject: [libvirt] [PATCH V2 8/8] docs: update Xen driver information 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.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Fri, 06 Apr 2018 20:45:41 +0000 (UTC) X-ZohoMail: RSF_0 Z_629925259 SPT_0 Content-Type: text/plain; charset="utf-8" Now that the old Xen driver is removed, update the drvxen page with current information on the libxl drvier and remove all the old cruft. Signed-off-by: Jim Fehlig --- New patch in V2 to update the Xen driver page. docs/drvxen.html.in | 91 +++++++++++++++++++++----------------------------= ---- 1 file changed, 35 insertions(+), 56 deletions(-) diff --git a/docs/drvxen.html.in b/docs/drvxen.html.in index d30ed2a04..b8d190c94 100644 --- a/docs/drvxen.html.in +++ b/docs/drvxen.html.in @@ -2,20 +2,20 @@ -

Xen hypervisor driver

+

libxl hypervisor driver for Xen

=20
    =20

    - The libvirt Xen driver provides the ability to manage virtual machin= es - on any Xen release from 3.0.1 onwards. + The libvirt libxl driver provides the ability to manage virtual + machines on any Xen release from 4.4.0 onwards.

    =20

    Project Links

    =20
    • - The Xen + The Xen hypervisor on Linux and Solaris hosts
    @@ -23,54 +23,23 @@

    Deployment pre-requisites

    =20

    - The libvirt Xen driver uses a combination of channels to manage Xen - virtual machines. + The libvirt libxl driver uses Xen's libxl API, also known as + libxenlight, to implement libvirt's hypervisor driver + functionality. libxl provides a consolidated interface for + managing a Xen host and its virtual machines, unlike old + versions of Xen where applications often had to communicate + with xend, xenstored, and the hypervisor itself via hypercalls. + With libxl the only pre-requisit is a properly installed Xen + host with the libxl toolstack running in a service domain + (often Domain-0).

    =20 -
      -
    • - XenD: Access to the Xen daemon is a mandatory - requirement for the libvirt Xen driver. It requires that the UNIX - socket interface be enabled in the /etc/xen/xend-config.sxp<= /code> - configuration file. Specifically the config settings - (xend-unix-server yes). This path is usually restrict= ed - to only allow the root user access. As an alternative, - the HTTP interface can be used, however, this has significant secu= rity - implications. -
      • -
    • - XenStoreD: Access to the Xenstore daemon enables - more efficient codepaths for looking up domain information which - lowers the CPU overhead of management. -
      • -
    • - Hypercalls: The ability to make direct hypercalls - allows the most efficient codepaths in the driver to be used for - monitoring domain status. -
      • -
    • - XM config: When using Xen releases prior to 3.0.4, - there is no inactive domain management in XenD. For such releases, - libvirt will automatically process XM configuration files kept in - the /etc/xen directory. It is important not to place - any other non-config files in this directory. -
      • -
    • - libxl: Starting with Xen 4.2, the legacy XenD/xm - toolstack is deprecated in favor of libxl, also commonly called - libxenlight. libvirt supports this new Xen toolstack via the - libxl driver. If XenD is enabled, the legacy xen driver consisting - of the above mentioned channels will be used. If XenD is disabled, - the libxl driver will be used. -
      • -
    - -

    Connections to Xen driver

    +

    Connections to libxl driver

    =20

    - The libvirt Xen driver is a single-instance privileged driver, - with a driver name of 'xen'. Some example connection URIs for - the libvirt driver are: + The libvirt libxl driver is a single-instance privileged driver, + with a driver name of 'xen'. Some example connection URIs for + the libxl driver are:

    =20 
    @@ -83,18 +52,28 @@ xen+ssh://root@example.com/    (remote access, SSH tunn=
elled)
=20
     
    Import and export of libvirt domain XML configs=

    
=20
-    
    The Xen driver currently supports two native
-      config formats. The first known as xen-xm is the format
-      used by the XM tool for files in /etc/xen. The second
-      known as xen-sxpr, is the format used for interacting
-      with the XenD's legacy HTTP RPC service.
    
+    
    
+      The libxl driver currently supports three native
+      config formats. The first, known as xen-xm, is the
+      original Xen virtual machine config format used by the legacy
+      xm/xend toolstack. The second, known as xen-sxpr,
+      is also one of the original formats that was used by xend's
+      legacy HTTP RPC service. For compatibility, import and export
+      of these legacy formats is supported by the libxl driver.
+    
    
+
+    
    
+      The third format is xen-xl, which is the virtual
+      machine config format supported by modern Xen. The xen-xl
+      format is described in the xl.cfg(5) man page.
+    
    
=20
     
    Converting from XM config files to domain XML<=
/a>
    
=20
     
    
       The virsh domxml-from-native provides a way to convert =
an
-      existing set of XM config files into a guest description using libvi=
rt Domain XML
-      that can then be used by libvirt.
+      existing set of xl, xm, or sxpr config files to libvirt Domain XML,
+      which can then be used by libvirt.
     
    
=20
     
    $ virsh -c xen:/// domxml-from-native xen-xm rhel5.cfg
@@ -139,7 +118,7 @@ xen+ssh://root@example.com/    (remote access, SSH tunn=
elled)
=20
     
    
       The virsh domxml-to-native provides a way to convert a
-      guest description using libvirt Domain XML, into the XM config file
+      guest description using libvirt Domain XML into xl, xm, or sxpr conf=
ig
       format.
     
    
=20
--=20
2.16.3

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list