[Xen-changelog] Updated README for xm-test for the new "--with-vmx-kernel=KERNEL"

[Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User stekloff@xxxxxxxxxxxxxxxxxxxxxxxxxx
# Node ID cd68f36807f931106121e017be535741fd52515a
# Parent  eb364ce00a2415421992501a30977e7cc7c5cf48
Updated README for xm-test for the new "--with-vmx-kernel=KERNEL"
configuration option.

Signed-off-by: Daniel Stekloff <dsteklof@xxxxxxxxxx>

diff -r eb364ce00a24 -r cd68f36807f9 tools/xm-test/README
--- a/tools/xm-test/README      Wed Jan 25 23:06:39 2006
+++ b/tools/xm-test/README      Wed Jan 25 23:06:46 2006
@@ -70,10 +70,19 @@
 If HVM / VMX support is enabled, the ramdisk/bin/create_disk_image script
 will be run to create a full virt disk.img in the ramdisk directory. The
 script, by default, will look in /boot for the first non-Xen kernel it
-runs across. If you wish to use a different kernel or the script fails
-to find a kernel, please run the script manually to make a disk.img 
-using the -k option. Xm-test will look for disk.img in the ramdisk
-directory when run by default.
+runs across. If you'd like to set xm-test to use a specific kernel,
+rather than the first one it finds in /boot, you can configure it in
+with the "--with-vmx-kernel=KERNEL" option:
+
+# ./autogen
+# ./configure --enable-vmx-support --with-vmx-kernel=KERNEL
+# make
+
+Otherwise, you can always rerun the create script using the -k option
+to use a specific kernel. 
+
+Xm-test will look for disk.img in the ramdisk directory when run by 
+default.
 
 
 Running

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