ia64/xen-unstable

changeset 7889:7f8969754896

added block device content, including finding a few more bugs in xen
author sean@dague.net
date Fri Nov 18 12:58:16 2005 +0100 (2005-11-18)
parents 5b5f1b0aca33
children 60bb9e11bd7d
files docs/man/xm.pod.1
line diff
     1.1 --- a/docs/man/xm.pod.1	Fri Nov 18 12:42:59 2005 +0100
     1.2 +++ b/docs/man/xm.pod.1	Fri Nov 18 12:58:16 2005 +0100
     1.3 @@ -626,12 +626,62 @@ event.
     1.4  
     1.5  =item B<block-attach> I<domain-id> I<be-dev> I<fe-dev> I<mode> I<[bedomain-id]>
     1.6  
     1.7 -Create a new virtual block device
     1.8 +Create a new virtual block device.  This will trigger a hotplug event
     1.9 +for the guest.
    1.10 +
    1.11 +B<OPTIONS>
    1.12 +
    1.13 +=over 4
    1.14 +
    1.15 +=item I<domain-id>
    1.16 +
    1.17 +The domain id of the guest domain that the device will be attached to.
    1.18 +
    1.19 +=item I<be-dev>
    1.20 +
    1.21 +The device in the backend domain (usually domain 0) to be exported.
    1.22 +This can be specified as a physical partition (phy:sda7) or as a file
    1.23 +mounted as loopback (file://path/to/loop.iso).
    1.24 +
    1.25 +=item I<fe-dev>
    1.26 +
    1.27 +How the device should be presented to the guest domain.  It can be
    1.28 +specified as either a symbolic name, such as /dev/hdc, for common
    1.29 +devices, or by device id, such as 0x1400 (/dev/hdc device id in hex).
    1.30 +
    1.31 +=item I<mode>
    1.32 +
    1.33 +The access mode for the device from the guest domain.  Supported modes
    1.34 +are I<rw> (read/write) or I<ro> (read-only).
    1.35 +
    1.36 +=item I<bedomain-id>
    1.37 +
    1.38 +The back end domain hosting the device.  This defaults to domain 0.
    1.39 +
    1.40 +=back
    1.41 +
    1.42 +B<EXAMPLES>
    1.43 +
    1.44 +=over 4
    1.45 +
    1.46 +=item I<Mount an ISO as a Disk>
    1.47 +
    1.48 +xm block-attach guestdomain file://path/to/dsl-2.0RC2.iso /dev/hdc ro
    1.49 +
    1.50 +This will mount the dsl iso as /dev/hdc in the guestdomain as a read
    1.51 +only device.  This will probably not be detected as a cdrom by the
    1.52 +guest, but mounting /dev/hdc manually will work.
    1.53 +
    1.54 +=back
    1.55  
    1.56  =item B<block-detach> I<domain-id> I<devid>
    1.57  
    1.58 -Destroy a domain's virtual block device. DevId may either be a device
    1.59 -ID or the device name as mounted in the guest.
    1.60 +Destroy a domain's virtual block device. devid B<must> be the device
    1.61 +id given to the device by domain 0.  You will need to run I<xm
    1.62 +block-list> to determine that number.
    1.63 +
    1.64 +FIXME: this is currently B<broken>.  Even though a block device is
    1.65 +removed from domU, it appears to still be allocated in the domain 0.
    1.66  
    1.67  =item B<block-list> I<domain-id>
    1.68  
    1.69 @@ -722,7 +772,7 @@ Delete a vnet.
    1.70  
    1.71  =head1 SEE ALSO
    1.72  
    1.73 -B<xmdomain.cfg>(5)
    1.74 +B<xmdomain.cfg>(5), B<xentop>(1)
    1.75  
    1.76  BVT scheduling paper: K.J. Duda and D.R. Cheriton. Borrowed Virtual
    1.77  Time (BVT) scheduling: supporting latency-sensitive threads in a