i'm running opensuse 11.2. concurrent install of multiple kernels is no problem.
i've installed opensuse's xen4 from rpm
rpm -qa | grep -i ^xen
xen-tools-4.0.0_20873_01-29.1.x86_64
xen-4.0.0_20873_01-29.1.x86_64
xen-libs-4.0.0_20873_01-29.1.x86_64
which installs,
ls -al /boot | grep " xen"
-rw-r--r-- 1 root root 672804 2010-01-29 13:11
xen-4.0.0_20873_01-29.1.gz
lrwxrwxrwx 1 root root 26 2010-02-03 18:32 xen-4.0.gz ->
xen-4.0.0_20873_01-29.1.gz
lrwxrwxrwx 1 root root 26 2010-02-03 18:32 xen-4.gz ->
xen-4.0.0_20873_01-29.1.gz
lrwxrwxrwx 1 root root 26 2010-02-03 18:32 xen.gz ->
xen-4.0.0_20873_01-29.1.gz
lrwxrwxrwx 1 root root 28 2010-02-03 18:32 xen-syms ->
xen-syms-4.0.0_20873_01-29.1
-rw-r--r-- 1 root root 10451302 2010-01-29 13:11
xen-syms-4.0.0_20873_01-29.1
its relevant dirs, configs, bins, etc are in "all the usual places"
... /etc/xen, /var/lib/{xen/,xend/, xenstored}, etc.
for testing/debugging pvops+xen-unstable on opensuse, and in
comparison to its repo-based install, i'd like to do a parallel, fully
independent install of upstream's Xen4 from source on the same box.
to that end, i've
vi xen-unstable.hg/xen/Rules.mk
...
- TARGET := $(BASEDIR)/xen
+ TARGET := $(BASEDIR)/xen-upstream
...
and @ build,
make -j8 PREFIX=/usr/local/xen-upstream install-xen install-tools
i end up with,
ls -al /boot | grep upstream
-rw-r--r-- 1 root root 660724 2010-02-03 21:56
xen-upstream-4.0.0-rc3-pre.gz
lrwxrwxrwx 1 root root 29 2010-02-03 21:56
xen-upstream-4.0.gz -> xen-upstream-4.0.0-rc3-pre.gz
lrwxrwxrwx 1 root root 29 2010-02-03 21:56
xen-upstream-4.gz
-> xen-upstream-4.0.0-rc3-pre.gz
lrwxrwxrwx 1 root root 29 2010-02-03 21:56
xen-upstream.gz ->
xen-upstream-4.0.0-rc3-pre.gz
-rw-r--r-- 1 root root 9799389 2010-02-03 21:56
xen-upstream-syms-4.0.0-rc3-pre
so that's nicely separated, and,
ls /usr/local/xen-upstream/
bin/ etc/ include/ lib/ lib64/ sbin/ share/
ls /usr/local/xen-upstream/{etc/init.d,sbin/xend}
/usr/local/xen-upstream/sbin/xend
/usr/local/xen-upstream/etc/init.d:
xend xendomains
etc etc
i can, of course, start the 'upstream' services from this tree, but
they still seem to expect configs, scripts, dbs, etc in the default
locations -- i.e., it'd share the existing install's data.
i can patch code in src to look in other locations, but that's not
ideal. what's the RIGHT way to completely isolate the 2nd install,
and have its bins look for data/config in a uniques/specified
location? is a set of make params correct/sufficient?
thanks.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home