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-devel] [PATCH 21/21] xenpaging: (sparse) documenation

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH 21/21] xenpaging: (sparse) documenation
From: Olaf Hering <olaf@xxxxxxxxx>
Date: Fri, 26 Nov 2010 14:49:22 +0100
Delivery-date: Fri, 26 Nov 2010 06:15:18 -0800
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1290779363; l=1826; s=domk; d=aepfle.de; h=References:Subject:To:From:Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=hfyU/OZoYPdvsHFu8P2vYpT7c9c=; b=M75Gb1z7cRplADEwGdTqGtDBGOI1vedgmxgSjSYUBF0y77lGZN7XInteoj8KWjSqtOQ y/Vh04vkmwIYWTxTOPaWjkFIq7Q45x16PfZqFh/JPbfcyNRec+8UzHqwGxfepTmRoFQFH MmPLYnK5ZVZtKx4+PUR7cgoKh728MuwGG7A=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20101126134901.384130351@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: quilt/0.48-4.4
Write up some sparse documentation about xenpaging usage.

Signed-off-by: Olaf Hering <olaf@xxxxxxxxx>

 docs/misc/xenpaging.txt |   48 ++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 48 insertions(+)

--- /dev/null
+++ xen-unstable.hg-4.1.22433/docs/misc/xenpaging.txt
@@ -0,0 +1,48 @@
+The xenpaging code is new and not fully debugged.
+Usage of xenpaging can crash Xen or cause severe data corruption in the
+guest memory and its filesystems!
+xenpaging writes memory pages of a given guest to a file and moves the
+pages back to the pool of available memory.  Once the guests wants to
+access the paged-out memory, the page is read from disk and placed into
+memory.  This allows the sum of all running guests to use more memory
+than physically available on the host.
+Once the guest is running, run xenpaging with the guest_id and the
+number of pages to page-out:
+  chdir /var/lib/xen/xenpaging
+  xenpaging <guest_id>  <number_of_pages>
+To obtain the guest_id, run 'xm list'.
+xenpaging will write the pagefile to the current directory.
+Example with 128MB pagefile on guest 1:
+  xenpaging 1 32768
+Caution: stopping xenpaging manually will cause the guest to stall or
+crash because the paged-out memory is not written back into the guest!
+After a reboot of a guest, its guest_id changes, the current xenpaging
+binary has no target anymore. To automate restarting of xenpaging after
+guest reboot, specify the number if pages in the guest configuration
+file /etc/xen/vm/<guest_name>:
+Redo the guest with 'xm create /etc/xen/vm/<guest_name>' to activate the
+- implement stopping of xenpaging
+- implement/test live migration
+# vim: tw=72

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>