551c9a62bc
- Enable support for kernel decompression for gzip, bzip2, and LZMA
so that kernels compressed with any of these methods can be
launched.
- update xenalyze, more 64bit fixes
- allocate xentrace buffer metadata based on requested tbuf_size
xentrace.dynamic_sized_tbuf.patch
- fate#310510 - fix xenpaging
xenpaging.runtime_mru_size.patch
- specify policy mru size at runtime
xenpaging.no_domain_id.patch
- reduce memory usage in pager
- bnc#625394 - set vif mtu from bridge mtu if kernel supports it
vif-bridge.mtu.patch
- fate#310510 - fix xenpaging
xenpaging.autostart_delay.patch
- decouple create/destroycreateXenPaging from _create/_removeDevices
- change xenpaging variable from int to str
- init xenpaging variable to 0 if xenpaging is not in config file
to avoid string None coming from sxp file
OBS-URL: https://build.opensuse.org/package/show/Virtualization/xen?expand=0&rev=97
64 lines
1.9 KiB
Diff
64 lines
1.9 KiB
Diff
Subject: xenpaging: (sparse) documenation
|
|
|
|
Write up some sparse documentation about xenpaging usage.
|
|
|
|
Signed-off-by: Olaf Hering <olaf@aepfle.de>
|
|
|
|
---
|
|
docs/misc/xenpaging.txt | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
|
|
1 file changed, 48 insertions(+)
|
|
|
|
Index: xen-4.0.2-testing/docs/misc/xenpaging.txt
|
|
===================================================================
|
|
--- /dev/null
|
|
+++ xen-4.0.2-testing/docs/misc/xenpaging.txt
|
|
@@ -0,0 +1,48 @@
|
|
+Warning:
|
|
+
|
|
+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!
|
|
+
|
|
+Description:
|
|
+
|
|
+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.
|
|
+
|
|
+Usage:
|
|
+
|
|
+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>:
|
|
+
|
|
+xenpaging=32768
|
|
+
|
|
+Redo the guest with 'xm create /etc/xen/vm/<guest_name>' to activate the
|
|
+changes.
|
|
+
|
|
+
|
|
+Todo:
|
|
+- implement stopping of xenpaging
|
|
+- implement live migration
|
|
+
|
|
+
|
|
+# vim: tw=72
|