From 5ad4f375adb8ba6a8309cee15b073b965f41a21d Mon Sep 17 00:00:00 2001 From: "stekloff@elm3b216.beaverton.ibm.com" Date: Fri, 16 Dec 2005 11:50:27 +0000 Subject: Added information for running xm-test in HVM / VMX mode. Signed-off-by: Daniel Stekloff --- tools/xm-test/README | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/tools/xm-test/README b/tools/xm-test/README index f357019630..0d7e2507aa 100644 --- a/tools/xm-test/README +++ b/tools/xm-test/README @@ -55,6 +55,26 @@ you should not attempt to use a ramdisk from a previous minor version of xm-test (i.e., don't use a ramdisk from 0.4.0 with 0.5.0. 0.5.0 should work for 0.5.3 though) +If you'd like to build and run this with hardware virtual machine assist +(HVM) support to test fully virtualized disk images on VMX hardware, +please add the --enable-vmx-support option to configure: + + # ./autogen + # ./configure --enable-vmx-support + # make + +The ramdisk/bin/create_disk_image script, which builds the full virt +disk.img, requires Lilo 22.7+ to be installed on the system. Lilo is +used to install the bootloader on the disk.img. + +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. + Running ======= -- cgit v1.2.3