From nobody Mon Feb 9 14:14:34 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=1648469655; cv=none; d=zohomail.com; s=zohoarc; b=juSJzTyCLz2i7nxt5IW1fOfhy9B2b1q1Lr+VZolZ/BlyUU6gNpU6lxn/RYQ9pw/WUDgsjk+YhVoXmtOOoN57e1eR0+TnKOyC2+oE6Zi7qf6i3gKnw/uItXCiPmpn9HSDjyJX1FMffYTL6zpvhd0WoqwG1OYWjZ4gYb9v+ouWtpk= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1648469655; 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=uUKmoiUmst6nZ8zD6+S++6AOK1yCza6fJdxacaN3jzo=; b=R1UwYhl9RVpA+hqAEiGDZHLhH1pLUR7C+hlGxH0SRv83iZZwNQ99mNZdIBBMCg+JNndXxNuU8nYYo6zPU7wnltwv1ptjAFe3pfiB8EnuHdYuSd2vQF76qWF4/zD/8RG+oIqzgQwR/1lrF+8BAOfiMO1n2oIhB/meUf3jZf7N+2Q= 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 16484696550031018.3199447608694; Mon, 28 Mar 2022 05:14:15 -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-299-yc_jr5zsNZGV1bHkgOKdOw-1; Mon, 28 Mar 2022 08:11:08 -0400 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 02005899ED0; Mon, 28 Mar 2022 12:11:05 +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 DEC4B40FF411; Mon, 28 Mar 2022 12:11:04 +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 95DA6193F6D9; Mon, 28 Mar 2022 12:11:04 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id D0F241947BBE for ; Mon, 28 Mar 2022 12:11:00 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id B55EF1410F3B; Mon, 28 Mar 2022 12:11:00 +0000 (UTC) Received: from speedmetal.lan (unknown [10.40.208.35]) by smtp.corp.redhat.com (Postfix) with ESMTP id 3205F141DEF9 for ; Mon, 28 Mar 2022 12:11:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1648469653; 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=uUKmoiUmst6nZ8zD6+S++6AOK1yCza6fJdxacaN3jzo=; b=fSIP3jXuA71MCKgzW6YeKJ5DXSVpkOSF4SBBh4Y7PAuUHkxoKEwziTF52tIAZKV41dYvZM la2mr7fg8y5gPjDlQkeI6T5mQYadyVwN8cGPhLR2JwSMYskZV+WmRNYOpzn60Z025G0nGr NiboUuPhEj9OgOQKI58t4rM0+bfuEdQ= X-MC-Unique: yc_jr5zsNZGV1bHkgOKdOw-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 14/29] docs: Convert 'drvxen' page to rST Date: Mon, 28 Mar 2022 14:10:29 +0200 Message-Id: In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.85 on 10.11.54.7 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.84 on 10.11.54.2 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: 1648469657507100001 Content-Type: text/plain; charset="utf-8"; x-default="true" Fix the referenced anchor in 'formatdomain.rst' right away. Signed-off-by: Peter Krempa Reviewed-by: Erik Skultety --- docs/drvxen.html.in | 358 ------------------------------------------ docs/drvxen.rst | 338 +++++++++++++++++++++++++++++++++++++++ docs/formatdomain.rst | 2 +- docs/meson.build | 2 +- 4 files changed, 340 insertions(+), 360 deletions(-) delete mode 100644 docs/drvxen.html.in create mode 100644 docs/drvxen.rst diff --git a/docs/drvxen.html.in b/docs/drvxen.html.in deleted file mode 100644 index 95be36c879..0000000000 --- a/docs/drvxen.html.in +++ /dev/null @@ -1,358 +0,0 @@ - - - - -

libxl hypervisor driver for Xen

- -
    - -

    - The libvirt libxl driver provides the ability to manage virtual - machines on any Xen release from 4.6.0 onwards. -

    - -

    Project Links

    - -
      -
    • - The Xen - hypervisor on Linux and Solaris hosts -
      • -
    - -

    Deployment pre-requisites

    - -

    - 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). -

    - -

    Connections to libxl driver

    - -

    - 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: -

    - -
    -xen:///system                     (local access, direct)
-xen+unix:///system                (local access, via daemon)
-xen://example.com/system          (remote access, TLS/x509)
-xen+tcp://example.com/system      (remote access, SASl/Kerberos)
-xen+ssh://root@example.com/system (remote access, SSH tunnelled)
-
    - - -

    Location of configuration files

    - -

    - The libxl driver comes with sane default values. However, during its - initialization it reads a configuration file which offers system - administrator to override some of that default. The file is located - under /etc/libvirt/libxl.conf -

    - - -

    Import and export of libvirt domain XML configs=

    - -

    - 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 (removed in 5.6.0) -

    - -

    - 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. -

    - -

    Converting from XM config files to domain XML<= /a>

    - -

    - The virsh domxml-from-native provides a way to convert = an - existing set of xl, xm, or sxpr config files to libvirt Domain XML, - which can then be used by libvirt. -

    - - 
    $ virsh -c xen:///system domxml-from-native xen-xm rhel5.cfg
-<domain type=3D'xen'>
-  <name>rhel5pv</name>
-  <uuid>8f07fe28-753f-2729-d76d-bdbd892f949a</uuid>
-  <memory>2560000</memory>
-  <currentMemory>307200</currentMemory>
-  <vcpu>4</vcpu>
-  <bootloader>/usr/bin/pygrub</bootloader>
-  <os>
-    <type arch=3D'x86_64' machine=3D'xenpv'>linux</type>
-  </os>
-  <clock offset=3D'utc'/>
-  <on_poweroff>destroy</on_poweroff>
-  <on_reboot>restart</on_reboot>
-  <on_crash>restart</on_crash>
-  <devices>
-    <disk type=3D'file' device=3D'disk'>
-      <driver name=3D'tap' type=3D'aio'/>
-      <source file=3D'/var/lib/xen/images/rhel5pv.img'/>
-      <target dev=3D'xvda' bus=3D'xen'/>
-    </disk>
-    <disk type=3D'file' device=3D'disk'>
-      <driver name=3D'tap' type=3D'qcow'/>
-      <source file=3D'/root/qcow1-xen.img'/>
-      <target dev=3D'xvdd' bus=3D'xen'/>
-    </disk>
-    <interface type=3D'bridge'>
-      <mac address=3D'00:16:3e:60:36:ba'/>
-      <source bridge=3D'xenbr0'/>
-    </interface>
-    <console type=3D'pty'>
-      <target port=3D'0'/>
-    </console>
-    <input type=3D'mouse' bus=3D'xen'/>
-    <graphics type=3D'vnc' port=3D'-1' autoport=3D'yes' listen=3D'0.0.0=
.0'/>
-  </devices>
-</domain>
    - -

    Converting from domain XML to XM config files<= /a>

    - -

    - The virsh domxml-to-native provides a way to convert a - guest description using libvirt Domain XML into xl, xm, or sxpr conf= ig - format. -

    - - 
    $ virsh -c xen:///system domxml-to-native xen-xm rhel5pv.xml
-name =3D "rhel5pv"
-uuid =3D "8f07fe28-753f-2729-d76d-bdbd892f949a"
-maxmem =3D 2500
-memory =3D 300
-vcpus =3D 4
-bootloader =3D "/usr/bin/pygrub"
-kernel =3D "/var/lib/xen/boot_kernel.0YK-cS"
-ramdisk =3D "/var/lib/xen/boot_ramdisk.vWgrxK"
-extra =3D "ro root=3D/dev/VolGroup00/LogVol00 rhgb quiet"
-on_poweroff =3D "destroy"
-on_reboot =3D "restart"
-on_crash =3D "restart"
-sdl =3D 0
-vnc =3D 1
-vncunused =3D 1
-vnclisten =3D "0.0.0.0"
-disk =3D [ "tap:aio:/var/lib/xen/images/rhel5pv.img,xvda,w", "tap:qcow:/ro=
ot/qcow1-xen.img,xvdd,w" ]
-vif =3D [ "mac=3D00:16:3e:60:36:ba,bridge=3Dvirbr0,script=3Dvif-bridge,vif=
name=3Dvif5.0" ]
    - -

    Pass-through of arbitrary command-line argume= nts - to the qemu device model

    - -

    Since 6.7.0, the Xen driver supports p= assing - arbitrary command-line arguments to the qemu device model used by Xe= n with - the <xen:commandline> element under domain<= /code>. - In order to use command-line pass-through, an XML namespace request = must be - issued that pulls in http://libvirt.org/schemas/domain/xen/1.0= . - With the namespace in place, it is then possible to add - <xen:arg>sub-elements to - <xen:commandline> describing each argument passed= to - the device model when starting the domain. -

    -

    The following example illustrates passing arguments to the QEMU dev= ice - model that define a floppy drive, which Xen does not support through= its - public APIs: -

    - 
    -<domain type=3D"xen" xmlns:xen=3D"http://libvirt.org/schemas/domain/xen=
/1.0">
-  ...
-  <xen:commandline>
-    <xen:arg value=3D'-drive'/>
-    <xen:arg value=3D'file=3D/path/to/image,format=3Draw,if=3Dnone,id=
=3Ddrive-fdc0-0-0'/>
-    <xen:arg value=3D'-global'/>
-    <xen:arg value=3D'isa-fdc.driveA=3Ddrive-fdc0-0-0'/>
-  </xen:commandline>
-</domain>
-
    - -

    Example domain XML config

    - -

    - Below are some example XML configurations for Xen guest domains. - For full details of the available options, consult the domain XML format - guide. -

    - -

    Paravirtualized guest bootloader

    - -

    - Using a bootloader allows a paravirtualized guest to be booted using - a kernel stored inside its virtual disk image -

    - - 
    <domain type=3D'xen' >
-  <name>fc8</name>
-  <bootloader>/usr/bin/pygrub</bootloader>
-  <os>
-    <type>linux</type>
-  </os>
-  <memory>131072</memory>
-  <vcpu>1</vcpu>
-  <devices>
-    <disk type=3D'file'>
-      <source file=3D'/var/lib/xen/images/fc4.img'/>
-      <target dev=3D'sda1'/>
-    </disk>
-    <interface type=3D'bridge'>
-      <source bridge=3D'xenbr0'/>
-      <mac address=3D'aa:00:00:00:00:11'/>
-      <script path=3D'/etc/xen/scripts/vif-bridge'/>
-    </interface>
-    <console tty=3D'/dev/pts/5'/>
-  </devices>
-</domain>
    - -

    Paravirtualized guest direct kernel boot

    - -

    - For installation of paravirtualized guests it is typical to boot the - domain using a kernel and initrd stored in the host OS -

    - - 
    <domain type=3D'xen' >
-  <name>fc8</name>
-  <os>
-    <type>linux</type>
-    <kernel>/var/lib/xen/install/vmlinuz-fedora8-x86_64</kernel&g=
t;
-    <initrd>/var/lib/xen/install/initrd-vmlinuz-fedora8-x86_64</i=
nitrd>
-    <cmdline> kickstart=3Dhttp://example.com/myguest.ks </cmdline=
>
-  </os>
-  <memory>131072</memory>
-  <vcpu>1</vcpu>
-  <devices>
-    <disk type=3D'file'>
-      <source file=3D'/var/lib/xen/images/fc4.img'/>
-      <target dev=3D'sda1'/>
-    </disk>
-    <interface type=3D'bridge'>
-      <source bridge=3D'xenbr0'/>
-      <mac address=3D'aa:00:00:00:00:11'/>
-      <script path=3D'/etc/xen/scripts/vif-bridge'/>
-    </interface>
-    <graphics type=3D'vnc' port=3D'-1'/>
-    <console tty=3D'/dev/pts/5'/>
-  </devices>
-</domain>
    - -

    Fullyvirtualized guest BIOS boot

    - -

    - Fullyvirtualized guests use the emulated BIOS to boot off the primary - harddisk, CDROM or Network PXE ROM. -

    - - 
    <domain type=3D'xen' id=3D'3'>
-  <name>fv0</name>
-  <uuid>4dea22b31d52d8f32516782e98ab3fa0</uuid>
-  <os>
-    <type>hvm</type>
-    <loader>/usr/lib/xen/boot/hvmloader</loader>
-    <boot dev=3D'hd'/>
-  </os>
-  <memory>524288</memory>
-  <vcpu>1</vcpu>
-  <on_poweroff>destroy</on_poweroff>
-  <on_reboot>restart</on_reboot>
-  <on_crash>restart</on_crash>
-  <features>
-    <pae/>
-    <acpi/>
-    <apic/>
-  </features>
-  <clock sync=3D"localtime"/>
-  <devices>
-    <emulator>/usr/lib/xen/bin/qemu-dm</emulator>
-    <interface type=3D'bridge'>
-      <source bridge=3D'xenbr0'/>
-      <mac address=3D'00:16:3e:5d:c7:9e'/>
-      <script path=3D'vif-bridge'/>
-    </interface>
-    <disk type=3D'file'>
-      <source file=3D'/var/lib/xen/images/fv0'/>
-      <target dev=3D'hda'/>
-    </disk>
-    <disk type=3D'file' device=3D'cdrom'>
-      <source file=3D'/var/lib/xen/images/fc5-x86_64-boot.iso'/>
-      <target dev=3D'hdc'/>
-      <readonly/>
-    </disk>
-    <disk type=3D'file' device=3D'floppy'>
-      <source file=3D'/root/fd.img'/>
-      <target dev=3D'fda'/>
-    </disk>
-    <graphics type=3D'vnc' port=3D'5904'/>
-  </devices>
-</domain>
    - -

    Fullyvirtualized guest direct kernel boot

    - -

    - With Xen 3.2.0 or later it is possible to bypass the BIOS and direct= ly - boot a Linux kernel and initrd as a fullyvirtualized domain. This al= lows - for complete automation of OS installation, for example using the An= aconda - kickstart support. -

    - - 
    <domain type=3D'xen' id=3D'3'>
-  <name>fv0</name>
-  <uuid>4dea22b31d52d8f32516782e98ab3fa0</uuid>
-  <os>
-    <type>hvm</type>
-    <loader>/usr/lib/xen/boot/hvmloader</loader>
-    <kernel>/var/lib/xen/install/vmlinuz-fedora8-x86_64</kernel&g=
t;
-    <initrd>/var/lib/xen/install/initrd-vmlinuz-fedora8-x86_64</i=
nitrd>
-    <cmdline> kickstart=3Dhttp://example.com/myguest.ks </cmdline=
>
-  </os>
-  <memory>524288</memory>
-  <vcpu>1</vcpu>
-  <on_poweroff>destroy</on_poweroff>
-  <on_reboot>restart</on_reboot>
-  <on_crash>restart</on_crash>
-  <features>
-    <pae/>
-    <acpi/>
-    <apic/>
-  </features>
-  <clock sync=3D"localtime"/>
-  <devices>
-    <emulator>/usr/lib/xen/bin/qemu-dm</emulator>
-    <interface type=3D'bridge'>
-      <source bridge=3D'xenbr0'/>
-      <mac address=3D'00:16:3e:5d:c7:9e'/>
-      <script path=3D'vif-bridge'/>
-    </interface>
-    <disk type=3D'file'>
-      <source file=3D'/var/lib/xen/images/fv0'/>
-      <target dev=3D'hda'/>
-    </disk>
-    <disk type=3D'file' device=3D'cdrom'>
-      <source file=3D'/var/lib/xen/images/fc5-x86_64-boot.iso'/>
-      <target dev=3D'hdc'/>
-      <readonly/>
-    </disk>
-    <disk type=3D'file' device=3D'floppy'>
-      <source file=3D'/root/fd.img'/>
-      <target dev=3D'fda'/>
-    </disk>
-    <graphics type=3D'vnc' port=3D'5904'/>
-  </devices>
-</domain>
    - - - diff --git a/docs/drvxen.rst b/docs/drvxen.rst new file mode 100644 index 0000000000..c131d52c7a --- /dev/null +++ b/docs/drvxen.rst @@ -0,0 +1,338 @@ +.. role:: since + +=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 +libxl hypervisor driver for Xen +=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 + +.. contents:: + +The libvirt libxl driver provides the ability to manage virtual machines o= n any +Xen release from 4.6.0 onwards. + +Project Links +------------- + +- The `Xen `__ hypervisor on Linux and Solaris + hosts + +Deployment pre-requisites +------------------------- + +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, u= nlike +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 run= ning +in a service domain (often Domain-0). + +Connections to libxl driver +--------------------------- + +The libvirt libxl driver is a single-instance privileged driver, with a dr= iver +name of 'xen'. Some example connection URIs for the libxl driver are: + +:: + + xen:///system (local access, direct) + xen+unix:///system (local access, via daemon) + xen://example.com/system (remote access, TLS/x509) + xen+tcp://example.com/system (remote access, SASl/Kerberos) + xen+ssh://root@example.com/system (remote access, SSH tunnelled) + +Location of configuration files +------------------------------- + +The libxl driver comes with sane default values. However, during its +initialization it reads a configuration file which offers system administr= ator +to override some of that default. The file is located under +``/etc/libvirt/libxl.conf`` + +Import and export of libvirt domain XML configs +----------------------------------------------- + +The libxl driver currently supports three native config formats. The first, +known as ``xen-xm``, is the original Xen virtual machine config format use= d by +the legacy xm/xend toolstack. The second, known as ``xen-sxpr``, is also o= ne of +the original formats that was used by xend's legacy HTTP RPC service ( +:since:`removed in 5.6.0` ) + +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. + +Converting from XM config files to domain XML +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The ``virsh domxml-from-native`` provides a way to convert an existing set= of +xl, xm, or sxpr config files to libvirt Domain XML, which can then be used= by +libvirt. + +:: + + $ virsh -c xen:///system domxml-from-native xen-xm rhel5.cfg + + rhel5pv + 8f07fe28-753f-2729-d76d-bdbd892f949a + 2560000 + 307200 + 4 + /usr/bin/pygrub + + linux + + + destroy + restart + restart + + + + + + + + + + + + + + + + + + + + + + + +Converting from domain XML to XM config files +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The ``virsh domxml-to-native`` provides a way to convert a guest descripti= on +using libvirt Domain XML into xl, xm, or sxpr config format. + +:: + + $ virsh -c xen:///system domxml-to-native xen-xm rhel5pv.xml + name =3D "rhel5pv" + uuid =3D "8f07fe28-753f-2729-d76d-bdbd892f949a" + maxmem =3D 2500 + memory =3D 300 + vcpus =3D 4 + bootloader =3D "/usr/bin/pygrub" + kernel =3D "/var/lib/xen/boot_kernel.0YK-cS" + ramdisk =3D "/var/lib/xen/boot_ramdisk.vWgrxK" + extra =3D "ro root=3D/dev/VolGroup00/LogVol00 rhgb quiet" + on_poweroff =3D "destroy" + on_reboot =3D "restart" + on_crash =3D "restart" + sdl =3D 0 + vnc =3D 1 + vncunused =3D 1 + vnclisten =3D "0.0.0.0" + disk =3D [ "tap:aio:/var/lib/xen/images/rhel5pv.img,xvda,w", "tap:qcow:= /root/qcow1-xen.img,xvdd,w" ] + vif =3D [ "mac=3D00:16:3e:60:36:ba,bridge=3Dvirbr0,script=3Dvif-bridge,= vifname=3Dvif5.0" ] + +Pass-through of arbitrary command-line arguments to the qemu device model +------------------------------------------------------------------------- + +:since:`Since 6.7.0` , the Xen driver supports passing arbitrary command-l= ine +arguments to the qemu device model used by Xen with the ```` +element under ``domain``. In order to use command-line pass-through, an XML +namespace request must be issued that pulls in +``http://libvirt.org/schemas/domain/xen/1.0``. With the namespace in place= , it +is then possible to add ````\ sub-elements to ``= `` +describing each argument passed to the device model when starting the doma= in. + +The following example illustrates passing arguments to the QEMU device mod= el +that define a floppy drive, which Xen does not support through its public = APIs: + +:: + + + ... + + + + + + + + +Example domain XML config +------------------------- + +Below are some example XML configurations for Xen guest domains. For full +details of the available options, consult the `domain XML +format `__ guide. + +Paravirtualized guest bootloader +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Using a bootloader allows a paravirtualized guest to be booted using a ker= nel +stored inside its virtual disk image + +:: + + + fc8 + /usr/bin/pygrub + + linux + + 131072 + 1 + + + + + + + + +