From 3292123d1374bb0b94c2889f376ef743f136da50 Mon Sep 17 00:00:00 2001 From: Daniel Veillard Date: Mon, 10 Sep 2007 15:16:25 +0000 Subject: [PATCH] * docs/architecture.html docs/errors.html docs/format.html docs/libvir.html: fixing typos spotted by Eduardo Pereira Daniel --- ChangeLog | 5 +++++ docs/architecture.html | 2 +- docs/errors.html | 2 +- docs/format.html | 12 ++++++------ docs/libvir.html | 16 ++++++++-------- 5 files changed, 21 insertions(+), 16 deletions(-) diff --git a/ChangeLog b/ChangeLog index 3aa8676ece..2d1ce07ce9 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +Mon Sep 10 17:15:29 CEST 2007 Daniel Veillard + + * docs/architecture.html docs/errors.html docs/format.html + docs/libvir.html: fixing typos spotted by Eduardo Pereira + Mon Sep 10 13:46:05 CEST 2007 Daniel Veillard * src/xend_internal.c: applied patch from Hugh Brock to allow diff --git a/docs/architecture.html b/docs/architecture.html index cbff79a941..74a290f63b 100644 --- a/docs/architecture.html +++ b/docs/architecture.html @@ -48,7 +48,7 @@ Store one, the Hypervisor hypercall are all isolated in separate C modules implementing at least a subset of the common operations defined by the drivers present in driver.h:

  • xend_internal: implements the driver functions though the Xen Daemon
    • -
  • xs_internal: implements the subset of the driver availble though the +
  • xs_internal: implements the subset of the driver available though the Xen Store
  • xen_internal: provide the implementation of the functions possible via direct hypervisor access
    • diff --git a/docs/errors.html b/docs/errors.html index c3292a8320..fa448f140c 100644 --- a/docs/errors.html +++ b/docs/errors.html @@ -65,5 +65,5 @@ this point, see the error.py example about it:

    def handler(ctxt, err):
     errno = err
 
 libvirt.registerErrorHandler(handler, 'context')

    the second argument to the registerErrorHandler function is passed as the -fist argument of the callback like in the C version. The error is a tuple +first argument of the callback like in the C version. The error is a tuple containing the same field as a virError in C, but cast to Python.

    main menu

    related links

    Graphics and design by Diana Fong

    diff --git a/docs/format.html b/docs/format.html index 059ec7e820..efdbcde194 100644 --- a/docs/format.html +++ b/docs/format.html @@ -59,7 +59,7 @@ significant:

    • name: the domain name, preferably ASCII based

    The format of the devices and their type may grow over time, but the following should be sufficient for basic use:

    A disk device indicates a block device, it can have two values for the type attribute either 'file' or 'block' corresponding to the 2 -options availble at the Xen layer. It has two mandatory children, and one +options available at the Xen layer. It has two mandatory children, and one optional one in no specific order:

    • source with a file attribute containing the path in Domain 0 to the file or a dev attribute if using a block device, containing the device name ('hda5' or '/dev/hda5')
      • @@ -72,7 +72,7 @@ guest, it also has a type whose value is currently 'bridge', it also have a number of children in no specific order:

      • source: indicating the bridge name
      • mac: the optional mac address provided in the address attribute
      • ip: the optional IP address provided in the address attribute
        • -
      • script: the script used to bridge the interfcae in the Domain 0
        • +
      • script: the script used to bridge the interface in the Domain 0
      • target: and optional target indicating the device name.

      A console element describes a serial console connection to the guest. It has no children, and a single attribute tty which @@ -237,11 +237,11 @@ support a variety of options:

      1. Userspace SLIRP stack
      2. Virtual network

        Provides a virtual network using a bridge device in the host. Depending on the virtual network configuration, the network may be - totally isolated,NAT'ing to aan explicit network device, or NAT'ing to + totally isolated, NAT'ing to an explicit network device, or NAT'ing to the default route. DHCP and DNS are provided on the virtual network in all cases and the IP range can be determined by examining the virtual network config with 'virsh net-dumpxml <network - name>'. There is one virtual network called'default' setup out + name>'. There is one virtual network called 'default' setup out of the box which does NAT'ing to the default route and has an IP range of 192.168.22.0/255.255.255.0. Each guest will have an associated tun device created with a name of vnetN, which can also be @@ -311,7 +311,7 @@ support a variety of options:

        1. Userspace SLIRP stack
        2. TCP tunnel

          A TCP client/server architecture provides a virtual network. One VM - provides the server end of the netowrk, all other VMS are configured as + provides the server end of the network, all other VMS are configured as clients. All network traffic is routed between the VMs via the server. This mode is also available to unprivileged users. There is no default DNS or DHCP support and no outgoing network access. To provide outgoing @@ -411,7 +411,7 @@ BIOS you will see

          <capabilities>
     </features>
   </guest>
   ...
-</capabilities>

          The fist block (in red) indicates the host hardware capbilities, currently +</capabilities>

          The first block (in red) indicates the host hardware capbilities, currently it is limited to the CPU properties but other information may be available, it shows the CPU architecture, and the features of the chip (the feature block is similar to what you will find in a Xen fully virtualized domain diff --git a/docs/libvir.html b/docs/libvir.html index 94567c66bb..04e2d39d13 100644 --- a/docs/libvir.html +++ b/docs/libvir.html @@ -585,7 +585,7 @@ drivers present in driver.h:

          • xend_internal: implements the driver functions though the Xen Daemon
            • -
          • xs_internal: implements the subset of the driver availble though the +
          • xs_internal: implements the subset of the driver available though the Xen Store
          • xen_internal: provide the implementation of the functions possible via direct hypervisor access
            • @@ -715,7 +715,7 @@ following should be sufficient for basic use:

            A disk device indicates a block device, it can have two values for the type attribute either 'file' or 'block' corresponding to the 2 -options availble at the Xen layer. It has two mandatory children, and one +options available at the Xen layer. It has two mandatory children, and one optional one in no specific order:

            • source with a file attribute containing the path in Domain 0 to the @@ -734,7 +734,7 @@ number of children in no specific order:

            • source: indicating the bridge name
            • mac: the optional mac address provided in the address attribute
            • ip: the optional IP address provided in the address attribute
              • -
            • script: the script used to bridge the interfcae in the Domain 0
              • +
            • script: the script used to bridge the interface in the Domain 0
            • target: and optional target indicating the device name.
            @@ -944,11 +944,11 @@ support a variety of options:

          • Virtual network

            Provides a virtual network using a bridge device in the host. Depending on the virtual network configuration, the network may be - totally isolated,NAT'ing to aan explicit network device, or NAT'ing to + totally isolated, NAT'ing to an explicit network device, or NAT'ing to the default route. DHCP and DNS are provided on the virtual network in all cases and the IP range can be determined by examining the virtual network config with 'virsh net-dumpxml <network - name>'. There is one virtual network called'default' setup out + name>'. There is one virtual network called 'default' setup out of the box which does NAT'ing to the default route and has an IP range of 192.168.22.0/255.255.255.0. Each guest will have an associated tun device created with a name of vnetN, which can also be @@ -1018,7 +1018,7 @@ support a variety of options:

          • TCP tunnel

            A TCP client/server architecture provides a virtual network. One VM - provides the server end of the netowrk, all other VMS are configured as + provides the server end of the network, all other VMS are configured as clients. All network traffic is routed between the VMs via the server. This mode is also available to unprivileged users. There is no default DNS or DHCP support and no outgoing network access. To provide outgoing @@ -1140,7 +1140,7 @@ BIOS you will see

            ... </capabilities> -

            The fist block (in red) indicates the host hardware capbilities, currently +

            The first block (in red) indicates the host hardware capbilities, currently it is limited to the CPU properties but other information may be available, it shows the CPU architecture, and the features of the chip (the feature block is similar to what you will find in a Xen fully virtualized domain @@ -1361,7 +1361,7 @@ this point, see the error.py example about it:

            libvirt.registerErrorHandler(handler, 'context')

            the second argument to the registerErrorHandler function is passed as the -fist argument of the callback like in the C version. The error is a tuple +first argument of the callback like in the C version. The error is a tuple containing the same field as a virError in C, but cast to Python.

            FAQ