This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-changelog] added block device content, including finding a few more

To: xen-changelog@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-changelog] added block device content, including finding a few more bugs in xen
From: Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>
Date: Fri, 18 Nov 2005 20:14:06 +0000
Delivery-date: Fri, 18 Nov 2005 20:14:19 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-changelog-request@lists.xensource.com?subject=help>
List-id: BK change log <xen-changelog.lists.xensource.com>
List-post: <mailto:xen-changelog@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=unsubscribe>
Reply-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-changelog-bounces@xxxxxxxxxxxxxxxxxxx
# HG changeset patch
# User sean@xxxxxxxxx
# Node ID 7f89697548966f9235771e0c0b339180e8407e61
# Parent  5b5f1b0aca33e7a8bad04893ea6a948befea1c20
added block device content, including finding a few more bugs in xen

diff -r 5b5f1b0aca33 -r 7f8969754896 docs/man/xm.pod.1
--- a/docs/man/xm.pod.1 Fri Nov 18 11:42:59 2005
+++ b/docs/man/xm.pod.1 Fri Nov 18 11:58:16 2005
@@ -626,12 +626,62 @@
 =item B<block-attach> I<domain-id> I<be-dev> I<fe-dev> I<mode> I<[bedomain-id]>
-Create a new virtual block device
+Create a new virtual block device.  This will trigger a hotplug event
+for the guest.
+=over 4
+=item I<domain-id>
+The domain id of the guest domain that the device will be attached to.
+=item I<be-dev>
+The device in the backend domain (usually domain 0) to be exported.
+This can be specified as a physical partition (phy:sda7) or as a file
+mounted as loopback (file://path/to/loop.iso).
+=item I<fe-dev>
+How the device should be presented to the guest domain.  It can be
+specified as either a symbolic name, such as /dev/hdc, for common
+devices, or by device id, such as 0x1400 (/dev/hdc device id in hex).
+=item I<mode>
+The access mode for the device from the guest domain.  Supported modes
+are I<rw> (read/write) or I<ro> (read-only).
+=item I<bedomain-id>
+The back end domain hosting the device.  This defaults to domain 0.
+=over 4
+=item I<Mount an ISO as a Disk>
+xm block-attach guestdomain file://path/to/dsl-2.0RC2.iso /dev/hdc ro
+This will mount the dsl iso as /dev/hdc in the guestdomain as a read
+only device.  This will probably not be detected as a cdrom by the
+guest, but mounting /dev/hdc manually will work.
 =item B<block-detach> I<domain-id> I<devid>
-Destroy a domain's virtual block device. DevId may either be a device
-ID or the device name as mounted in the guest.
+Destroy a domain's virtual block device. devid B<must> be the device
+id given to the device by domain 0.  You will need to run I<xm
+block-list> to determine that number.
+FIXME: this is currently B<broken>.  Even though a block device is
+removed from domU, it appears to still be allocated in the domain 0.
 =item B<block-list> I<domain-id>
@@ -722,7 +772,7 @@
 =head1 SEE ALSO
+B<xmdomain.cfg>(5), B<xentop>(1)
 BVT scheduling paper: K.J. Duda and D.R. Cheriton. Borrowed Virtual
 Time (BVT) scheduling: supporting latency-sensitive threads in a

Xen-changelog mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-changelog] added block device content, including finding a few more bugs in xen, Xen patchbot -unstable <=