RE: [Xen-ia64-devel] Recipe for getting/building/running Xen/ia64

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

That is correct: No privify step is required if you are
using  http://xenbits.xensource.com/ext/xenlinux-ia64-2.6.12.hg
because all privilege-sensitive instructions have been
replaced with hypercalls.

> -----Original Message-----
> From: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx] 
> Sent: Tuesday, July 19, 2005 3:24 AM
> To: Magenheimer, Dan (HP Labs Fort Collins); 
> xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-ia64-devel] Recipe for 
> getting/building/running Xen/ia64
> 
> Good writing, and just one point I'm not sure yet. Is any 
> privify still
> required now on xenlinux, or all questionable instructions against
> virtualization have been changed to access shared info page?
> 
> Thanks,
> Kevin
> 
> >-----Original Message-----
> >From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> >[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> >Magenheimer, Dan (HP Labs Fort Collins)
> >Sent: Tuesday, July 19, 2005 3:40 AM
> >To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >Subject: [Xen-ia64-devel] Recipe for 
> getting/building/running Xen/ia64
> >
> >A lot has changed in Xen/ia64 since the README files in
> >arch/ia64/tools were written.  Attached is the first draft
> >of a recipe for getting/building/running Xen/ia64.
> >It will need some work, but if you are a Xen/ia64 "newbie"
> >and have been eager to give Xen/ia64 a try, please try
> >following this recipe and provide changes/feedback.
> >It will eventually find its way back into a README file.
> >
> >Thanks,
> >Dan
> >
> >=======
> >
> >Preparation:  On your ia64 system, you will need:
> >- python2.3, see http://www.python.org
> >- the mercurial (aka "hg") open-source source code 
> management software
> >  version >= 0.6b, see: http://www.selenic.com/mercurial/
> >- gcc version >= 3.2 (4.0 is not known to work yet though)
> >- a copy of linux 2.6.11 (tar file)
> >
> >Getting and building the Xen/ia64 "tip":
> >- create a directory to put it in:
> >     $ cd "HOME" # wherever you want to put it
> >     $ mkdir xen-ia64-unstable.hg
> >     $ cd xen-ia64-unstable.hg
> >- get the bits
> >     $ hg clone http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
> >     $ hg update
> >- unpack linux (many linux files are directly used by xen/ia64)
> >     $ cd "HOME"
> >     $ cp ..../linux-2.6.11.tar.gz .
> >     $ tar xzf linux-2.6.11.tar.gz
> >- build Xen/ia64
> >     $ cd "HOME"/xen-ia64-unstable.hg
> >     $ cd xen
> >     $ bash arch/ia64/tools/mkbuildtree
> >     $ make # if using the cross-compiler, use "make
> >XEN_TARGET_ARCH=ia64"
> >
> >
> >Getting and building the Xenlinux/ia64 "tip":
> >- create a directory to put it in:
> >     $ cd "HOME" # wherever you want to put it
> >     $ mkdir xenlinux-ia64-2.6.12.hg
> >     $ cd xenlinux-ia64-2.6.12.hg
> >- get the bits
> >     $ hg clone
> >http://xenbits.xensource.com/ext/xenlinux-ia64-2.6.12.hg
> >     $ hg update
> >- prep the xenlinux build
> >     $ cd "HOME"/xenlinux-ia64-2.6.12.hg
> >     $ cd include/asm-xen/
> >     $ ln -s asm-ia64 asm
> >     $ cd "HOME"/xenlinux-ia64-2.6.12.hg
> >     $ # following works for HP zx1-based systems
> >     $ cp arch/ia64/configs/xen_zx1defconfig .config
> >     $ # if you build your own .config, ensure that CONFIG_XEN=y
> >     $ # and there are no modules (replace all "=m" with "=y")
> >- build xenlinux
> >     $ cd "HOME"/xenlinux-ia64-2.6.12.hg
> >     $ yes "" | make oldconfig
> >     $ make
> >     $ # resulting xenlinux binary is called vmlinux
> >
> >- prep the bootloader
> >     $ # where is your elilo.conf file?  call this "BOOTDIR"
> >     $ # add an entry to "BOOTDIR"/elilo.conf
> >     $ # the exact syntax for the "append=" is very system
> >dependent...
> >     $ # the part before the '--' is for xen...
> >     $ # the part after the '--' should look like your normal linux
> >bootline
> >     $ # FIXME: not sure if nomca is still needed
> >             image=xen
> >             label=xen
> >             initrd=xenlinux
> >             read-only
> >             read-only
> >             append="sched=bvt -- nomca console=ttyS0,115200
> >root=/dev/sda2"
> >
> >Booting Xen/ia64:
> >     $ cd "HOME"/xen-ia64-unstable.hg
> >     $ cp xen "BOOTDIR"
> >     $ cd "HOME"/xenlinux-ia64-2.6.12.hg
> >     $ cp vmlinux "BOOTDIR"/xenlinux
> >     $ # if you see no output on your console, you may need to
> >specify
> >     $ # a com1= on the Xen part of the "append=" line.  Note that
> >the
> >     $ # syntax for this is different than for linux.  FIXME: docs
> >     $ # for this will be documented in a separate file
> >
> >_______________________________________________
> >Xen-ia64-devel mailing list
> >Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >http://lists.xensource.com/xen-ia64-devel
> 

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