[Xen-changelog] [xen-unstable] [IA64] update VTI Readme file

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

# HG changeset patch
# User awilliam@xxxxxxxxxxx
# Node ID dad1f890aca52bb0b90c920d9f16e4e870a8acde
# Parent  550786d7d3528653f269bb3b598e8a0b15b3d976
[IA64] update VTI Readme file

Update VTI how-to readme file with physical disk

Signed-off-by: Fred yang <Fred.Yang@xxxxxxxxx>
---
 xen/arch/ia64/tools/README.RunVT |   95 ++++++++++++++++-----------------------
 1 files changed, 41 insertions(+), 54 deletions(-)

diff -r 550786d7d352 -r dad1f890aca5 xen/arch/ia64/tools/README.RunVT
--- a/xen/arch/ia64/tools/README.RunVT  Mon Jul 03 08:12:16 2006 -0600
+++ b/xen/arch/ia64/tools/README.RunVT  Mon Jul 03 08:15:43 2006 -0600
@@ -1,59 +1,46 @@ INSTRUCTIONS FOR Running IPF/Xen with VT
 INSTRUCTIONS FOR Running IPF/Xen with VT-enabled Tiger4 pltform
 
-Note: the Domain0 must be an unmodified Linux
+1. Install a Linux Disk, VT_Disk, to be used by VT
+2. Setup the target VT_Disk
+       1. Boot VT_Disk
+       2. modify following files of VT_Disk
+               /boot/efi/efi/redhat/elilo.conf -
+                       modify "append=" line to have "root=/dev/hda3"
+                       ** note /dev/hda3 must reflect VT_Disk /root partition
 
-1) Perform operations in README.xenia64 to get a flattened Xen IPF source tree
+               /etc/fstab -
+                       LABEL=/     /     ext3    DEFAULTS  1   1
+                 to
+                       /dev/hda3   /     ext3    DEFAULTS  1   1
+                  and other entries accordingly
+3. Install Xen and boot XenLinux on your standard Linux disk
+        1. modify /boot/efi/efi/redhat/elilo.conf -
+                       "append=" entry to have "root=/dev/sda3"
+       2. modify /etc/fstab -
+                        LABEL=/     /     ext3    DEFAULTS  1   1
+                  to
+                        /dev/sda3   /     ext3    DEFAULTS  1   1
+                  and other entries accordingly
+4. Reboot XenLinux with VT_Disk in /dev/sdb slot
+       1. copy Guest_Firmware.bin into /usr/lib/xen/boot/guest_firmware.bin
+       2. modify /etc/xen/xmexample.vti
+               disk = [ 'phy:/dev/sdb,ioemu:hda,w' ]
+          and make sure
+               kernel=/usr/lib/xen/boot/guest_firmware.bin
+5. Make sure XenLinux has SDL installed by
+       > rpm -q -a | grep SDL
+               SDL-1.2.7-8 SDL-devel-1.2.7-8 
+6. Start vncserver from XenLinux
+       1. ifconfig  to get XenLinux IP address
+       2. vncserver
+7. Start VT Domain
+       1. From a remote system connect to XenLinux through vnc viewer
+       2. On vnc windows
+               > xend start
+               > xm create /etc/xen/xmexample.vti
+          an EFI shell will popup
+               > fs0:
+               fs0:> cd efi\redhat
+               fs0:> elilo linux
 
-2) Build an unmodified Linux 2.6 kernel
-       a) tar xvfz  linux-2.6.11.tar.gz
-        b) cp arch/ia64/configs/tiger_defconfig .config
-       c) Build linux.
-               1) yes "" | make oldconfig
-               2) make
 
-3) Build IPF VT-enabled Xen image
-       edit xen/arch/ia64/Rules.mk for
-               CONFIG_VTI      ?= y    to enable VT-enable build
-4) Setup ELILO.CONF
-       image=xen
-               label=xen
-               initrd=vmlinux2.6.11            // unmodified Linux kernel image
-               read-only
-               append="nomca root=/dev/sda3"
-
-STATUS as 4/28/05 - Features implemented for Domain0
-
-0. Runs unmodified Linux kernel as Domain0
-    Validated with Linux 2.6.11 to run Xwindow and NIC on UP logical processor
-
-1. Take advantage of VT-enabled processor
-   a. Processor intercepts guest privileged instruction and deliver 
Opcode/Cause to Hypervisor
-   b. One VPD (Virtual Processor Descriptor) per Virtual Processor
-   c. Domains are in a different virtual address space from hypervisor. 
Domains have one less VA bit than hypervisor, where hypervisor runs in 
0xF00000... address protected by the processor from Domains.
-
-2. vTLB and guest_VHPT
-   a. vTLB extending machine TLB entries through hypervisor internal data 
structure
-      vTLB caches Domains installed TR's and TC's, and then installs TC's for 
Domains instead.
-      vTLB implements collision chains
-   b. Processor walks hypervisor internal VHPT, not the domain VHPT.  On TLB 
miss, vTLB is consulted first to put hypervisor cached entry into VHPT without 
inject TLB miss to domain.
-
-3. Region ID fix-partitioning
-   a. currently hard partition 24bits of RIDs into 16 partitions by using top 
4bit.
-   b. Hypervisor uses the very last partition RIDs, i.e., 0xFxxxxx RIDs
-   c. Effectively supports Domain0 and 14 other DomainN
-
-4. HyperVisor is mapped with 2 sets of RIDs during runtime, its own RIDs and 
the active Domain RIDs
-   a. Domain RIDs are used by processor to access guest_VHPT during Domain 
runtime
-   b. Hypervisor RIDs are used when Hypervisor is running
-   c. Implies there are some Region registers transition on entering/exiting 
hypervisor
-
-5. Linux styled pt_regs with minor modification for VT and instruction 
emulation
-   a. Part of Domain registers are saved/restored from VPD
-   b. Extended pt_regs to include r4~r7 and Domain's iipa & isr for possible 
instruction emulation, so no need to save a complete set of switch_stack on IVT 
entry
-
-6. Linux styled per virtual processor memory/RSE stacks, which is the same as 
non-VT domain0
-
-7. Handles splitted I/DCache design
-   Newer IPF processors has split I/Dcaches.  The design takes this into 
consideration when Xen recopy Domain0 to target address for execution
-
-

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