[Xen-changelog] [xen-unstable] docs: update xenpaging.txt

[Xen patchbot-unstable <patchbot@xxxxxxx>]

# HG changeset patch
# User Olaf Hering <olaf@xxxxxxxxx>
# Date 1346345851 -3600
# Node ID 4e6bb38c3a40bb43d8b31374ec14a2b279b0fc24
# Parent  1e5fc9f79c0ecfd8c6a00640691717e40c58b87f
docs: update xenpaging.txt

Signed-off-by: Olaf Hering <olaf@xxxxxxxxx>
Committed-by: Keir Fraser <keir@xxxxxxx>
---


diff -r 1e5fc9f79c0e -r 4e6bb38c3a40 docs/misc/xenpaging.txt
--- a/docs/misc/xenpaging.txt   Thu Aug 30 17:55:31 2012 +0100
+++ b/docs/misc/xenpaging.txt   Thu Aug 30 17:57:31 2012 +0100
@@ -12,37 +12,34 @@ access the paged-out memory, the page is
 memory.  This allows the sum of all running guests to use more memory
 than physically available on the host.
 
+Requirements:
+
+xenpaging relies on Intel EPT or AMD RVI, other hardware is not
+supported. Only HVM guests are supported.  The dom0 kernel needs
+paging-aware backend drivers to handle paged granttable entries.
+Currently only dom0 kernels based on classic Xen Linux support this
+functionality.
+
 Usage:
 
-Once the guest is running, run xenpaging with the guest_id and the
-number of pages to page-out:
+Up to now xenpaging is not integrated into libxl/xend, so it has to be
+started manually for each guest.
 
-  chdir /var/lib/xen/xenpaging
-  xenpaging <guest_id>  <number_of_pages>
+Once the guest is running, run xenpaging with the guest_id and the path
+to the pagefile:
+ 
+ /usr/lib/xen/bin/xenpaging -f /path/to/page_file -d dom_id &
 
-To obtain the guest_id, run 'xm list'.
-xenpaging will write the pagefile to the current directory.
-Example with 128MB pagefile on guest 1:
+Once xenpaging runs it needs a memory target, which is the memory
+footprint of the guest. This value (in KiB) must be written manually to
+xenstore. The following example sets the target to 512MB:
 
-  xenpaging 1 32768
+ xenstore-write /local/domain/<dom_id>/memory/target-tot_pages $((1024*512))
 
-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>:
-
-xenpaging=32768
-
-Redo the guest with 'xm create /etc/xen/vm/<guest_name>' to activate the
-changes.
-
+Now xenpaging tries to page-out as many pages to keep the overall memory
+footprint of the guest at 512MB.
 
 Todo:
-- implement stopping of xenpaging
-- implement/test live migration
-
+- integrate xenpaging into libxl
 
 # vim: tw=72

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog