direct-io.hg

changeset 1934:28c90122f778

bitkeeper revision 1.1108.25.1 (41066d7d4Nz_AdmSO0fZS5s0l5Z16w)

More information about PCI configuration, backend domains and
further sources of help.
author mwilli2@equilibrium.research.intel-research.net
date Tue Jul 27 14:58:05 2004 +0000 (2004-07-27)
parents a83817a4f882
children 9711b428cf6a
files docs/user.tex
line diff
     1.1 --- a/docs/user.tex	Tue Jul 27 10:44:40 2004 +0000
     1.2 +++ b/docs/user.tex	Tue Jul 27 14:58:05 2004 +0000
     1.3 @@ -670,6 +670,50 @@ administration privileges.
     1.4  IO privileges can be assigned to allow a domain to drive PCI devices
     1.5  itself.  This is used for to support driver domains.
     1.6  
     1.7 +Setting backend privileges is currently only supported in SXP format
     1.8 +config files (??? is this true - there's nothing in xmdefaults,
     1.9 +anyhow).  To allow a domain to function as a backend for others,
    1.10 +somewhere within the {\tt vm} element of its configuration file must
    1.11 +be a {\tt backend} element of the form {\tt (backend ({\em type}))}
    1.12 +where {\tt \em type} may be either {\tt netif} or {\tt blkif},
    1.13 +according to the type of virtual device this domain will service.
    1.14 +After this domain has been built, Xend will connect all new and
    1.15 +existing {\em virtual} devices (of the appropriate type) to that
    1.16 +backend.
    1.17 +
    1.18 +Note that:
    1.19 +\begin{itemize}
    1.20 +\item a block backend cannot import virtual block devices from other
    1.21 +domains
    1.22 +\item a network backend cannot import virtual network devices from
    1.23 +other domains
    1.24 +\end{itemize}
    1.25 +
    1.26 +Thus (particularly in the case of block backends, which cannot import
    1.27 +a virtual block device as their root filesystem), you may need to boot
    1.28 +a backend domain from a ramdisk or a network device.
    1.29 +
    1.30 +The privilege to drive PCI devices may also be specified on a
    1.31 +per-device basis.  Xen will assign the minimal set of hardware
    1.32 +privileges to a domain that are required to control its devices.  This
    1.33 +can be configured in either format of configuration file:
    1.34 +
    1.35 +\begin{itemize}
    1.36 +\item SXP Format:
    1.37 +  Include {\tt device} elements
    1.38 +  {\tt (device (pci (bus {\em x}) (dev {\em y}) (func {\em z}))) } \\
    1.39 +  inside the top-level {\tt vm} element.  Each one specifies the address
    1.40 +  of a device this domain is allowed to drive ---
    1.41 +  the numbers {\em x},{\em y} and {\em z} may be in either decimal or
    1.42 +  hexadecimal format.
    1.43 +\item Flat Format: Include a list of PCI device addresses of the
    1.44 +  format: \\ {\tt pci = ['x,y,z', ...] } \\ where each element in the
    1.45 +  list is a string specifying the components of the PCI device
    1.46 +  address, separated by commas.  The components ({\tt \em x}, {\tt \em
    1.47 +  y} and {\tt \em z}) of the list may be formatted as either decimal
    1.48 +  or hexadecimal.
    1.49 +\end{itemize}
    1.50 +
    1.51  \section{Administration Domains}
    1.52  
    1.53  Administration privileges allow a domain to use the ``dom0
    1.54 @@ -812,4 +856,44 @@ domain).  Device IDs should be given in 
    1.55  not need to be hidden --- they are hidden implicitly, since guest OSes
    1.56  do not need to configure them.
    1.57  
    1.58 +\chapter{Further Support}
    1.59 +
    1.60 +If you have questions that are not answered by this manual, the
    1.61 +sources of information listed below may be of interest to you.  Note
    1.62 +that bug reports, suggestions and contributions related to the
    1.63 +software (or the documentation) should be sent to the Xen developers'
    1.64 +mailing list (address below).
    1.65 +
    1.66 +\section{Other documentation}
    1.67 +
    1.68 +For developers interested in porting operating systems to Xen, the
    1.69 +{\em Xen Interface Manual} is distributed in the \path{docs/}
    1.70 +directory of the Xen source distribution.
    1.71 +
    1.72 +\section{Online references}
    1.73 +
    1.74 +The official Xen web site is found at: \\
    1.75 +{\tt
    1.76 +http://www.cl.cam.ac.uk/Research/SRG/netos/xen/] }.
    1.77 +
    1.78 +Links to other
    1.79 +documentation sources are listed at: \\ {\tt
    1.80 +http://www.cl.cam.ac.uk/Research/SRG/netos/xen/documentation.html}.
    1.81 +
    1.82 +\section{Mailing lists}
    1.83 +
    1.84 +There are currently two official Xen mailing lists:
    1.85 +
    1.86 +\begin{description}
    1.87 +\item[xen-devel@lists.sourceforge.net] Used for development
    1.88 +discussions and requests for help.  Subscribe at: \\
    1.89 +http://lists.sourceforge.net/mailman/listinfo/xen-devel
    1.90 +\item[xen-announce@lists.sourceforge.net] Used for announcements only.
    1.91 +Subscribe at: \\ http://lists.sourceforge.net/mailman/listinfo/xen-announce
    1.92 +\end{description}
    1.93 +
    1.94 +Although there is no specific user support list, the developers try to
    1.95 +assist users who post on xen-devel.  As the bulk of traffic on this
    1.96 +list increases, a dedicated user support list may be introduced.
    1.97 +
    1.98  \end{document}