Saturday, March 22, 2008

Install Xen 3.2 on Ubuntu 7.10 Desktop (amd64)

Backported Mercurial from Ubuntu Hardy Heron

$ vi /etc/apt/sources.list and add this line to the
deb-src \
hardy main restricted universe multiverse

# apt-get update
# apt-get build-dep mercurial
# apt-get source -b mercurial
# dpkg -i mercurial_0.9.5-2_amd64.deb

Installed gcc:-

# apt-get install gcc gcc-3.4 gcc-4.1 libsdl1.2-dev \
make libz-dev uuid-dev libasound2-dev gcc libc6-dev \

Installed 2.6.22-14-xen ubuntu xen-kernel
# aptitude install linux-image-xen
to protect Gnome desktop environment, when kernel
would be loaded.

Dowloaded :-

1. Tuned Makefile when install openssl
2. Tuned Makefile when install zlib
to perform "make install" to folders expected by Xen 3.2
3.apt-get install libncurses5-dev

Installing openssl assigned:-
in Makefile

Installing zlib configured as follows :-
# ./configure --shared
# make
# make install (in Makefile prefix=/usr)

Actions above have been undertaken to avoid failure when running:-
# make tools

Compiling Xen:-

# cd /usr/src
# wget
# hg clone
# tar -xzf xen-3.2.0.tar.gz
# cd xen-3.2.0
# make all
# make install

# update-rc.d xend defaults 20 21
# update-rc.d xendomains defaults 21 20
# depmod
# mkinitramfs -o /boot/initrd.img-
# vi /etc/init.d/xend and insert before shell code:-

mkdir -p /var/run/xenstored
mkdir -p /var/lock/subsys

Update /boot/grub/menu.lst

title Xen 3.2.0 / Ubuntu 7.10, kernel
root (hd0,4)
kernel /boot/xen-3.2.0.gz
module /boot/vmlinuz- root=UUID=8f17d1a1-64ab-425a-9b53-71d20aa7893e ro
module /boot/initrd.img-

Boot into new kernel

SNV84 DomU has been installed and tested at
Xen 3.2 Ubuntu 7.10 Desktop Dom0 (64-bit).
Notice, that eth2 is ethernet interface connected to ADSL Modem acting as DHCP bridge
and reported by:-
# brctl show
as a xen bridge after tuning /etc/xen/xend-conf.sxp and rebooting into Xen 3.2 kernel.

Installation profile
name = 'Solaris84PVM'
memory = '1024'
disk = [ 'file:/usr/lib/xen-solaris/snv84.iso,6:cdrom,r','phy:/dev/sdb11,0,w']
vif = [ 'bridge = eth2' ]
bootloader = '/usr/bin/pygrub'
kernel = '/boot/platform/i86xpv/kernel/amd64/unix'
ramdisk = '/boot/amd64/x86.miniroot'
extra = '/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom'

Runtime profile
name = 'Solaris84PVM'
memory = '1024'
disk = [ 'phy:/dev/sdb11,0,w' ]
vif = [ 'bridge = eth2' ]


Friday, March 14, 2008

Install Solaris 01/08 HVM DomU (64-bit) at Xen 3.2 CentOS 5.1 Dom0 (x86_64)

This posting follows up "Install Solaris (SNV 84) DomU at Xen 3.2 CentOS 5.1 Dom0 (64 bit)" and provides brief description how to install 64-bit Solaris 01/08 HVM DomU
at Xen 3.2 CentOS 5.1 Dom0 (64-bit as well) despite installer puts this HVM in 32-bit mode by default.
I have to notice that attempt to install Solaris 10 U4 HVM
with similar installation profile still hangs at the beginning, Solaris installer
hangs at initial boot up immediately after passing grub menu.

Phyton profile has been used for install:-

name = "Solaris79"
builder = "hvm"
memory = "1024"
disk = ['phy:/dev/sdb8,ioemu:hda,w','file:/usr/lib/xen-solaris/snv79.iso,hdc:cdrom,r']
vif = [ 'type=ioemu,bridge=eth2' ]
device_model = "/usr/lib64/xen/bin/qemu-dm"
kernel = "/usr/lib/xen/boot/hvmloader"
serial = "pty" # enable serial console
on_reboot = 'restart'
on_crash = 'restart'

Go through normal SXDE installation and change profile for runtime:-

name = "Solaris79"
builder = "hvm"
memory = "1024"
disk = ['phy:/dev/sdb8,ioemu:hda,w']
vif = [ 'type=ioemu,bridge=eth2' ]
device_model = "/usr/lib64/xen/bin/qemu-dm"
kernel = "/usr/lib/xen/boot/hvmloader"
serial = "pty" # enable serial console
on_reboot = 'restart'
on_crash = 'restart'

During first startup modify grub entries for Solaris 01/08 HVM as follows:-

Press "b" and proceed with booting :-

When logged in make permanent changes to file "/boot/grub/menu.lst" replacing
$ISADIR by "amd64" in corresponding lines.

Start NetBeans 6.0 to deploy and run a couple of sample Enterprise Java apllications to make sure GlassFish V2 and IDE itself won't malfunction after changes been done
to Solaris 01/08 HVM DomU.

1.Install Solaris (SNV 84) DomU at Xen 3.2 CentOS 5.1 Dom0 (64 bit)

Thursday, March 13, 2008

GNOME crashing on SNV84 DomU at Xen 3.2 CentOS 5.1 Dom0.

Install Solaris (SNV 84) DomU at Xen 3.2 CentOS 5.1 Dom0 (64 bit)

This posting is targeting cloning Mercurial Repository for Xen 3.2 on CentOS 5.1 and creating 64-bit Xen 3.2 CentOS 5.1 Dom0. To verify Dom0 functionality Solaris
(Navada Build 84) has been installed as DomU. Xvnc has been set up per Sun manuals
and it appeared that only CDE Desktop was functional on DomU. Gnome Desktop
crashed immediately after logging in.
However , that’s quite enough to perform Oracle 10g R2 installation at DomU
and evaluate I/0 performance provided by new Xen Hypervisor for Solaris Paravirtual guests.

First install Xen 3.2 from mercurial repository on xen-disabled CentOS 5.1 instance

# cd /usr/src/
# hg clone
# cd xen-3.2-testing.hg
# make world
# make install

Determine the name of the Xen Linux kernel version that was installed.

# ls /lib/modules

There should be a directory for the Xen Linux kernel (e.g.,
Generate the module dependency list and map files

# /sbin/depmod

Create the Xen initial ramdisk image

# /sbin/mkinitrd /boot/initrd-

Disable tls

# mv /lib64/tls /lib64/tls.disabled

Set xend service to start

# /sbin/chkconfig --add xend
# /sbin/chkconfig xend on

Edit /boot/grub/grub.conf and copy one of the existing boot entries to make the
required changes for Xen and reboot into new kernel.

title Xen-3.2 x86_64 (
root (hd1,4)
kernel /xen-3.2.gz
module /vmlinuz- ro root=/dev/VolGroup01/LogVol00 rhgb quiet
module /initrd-

eth2 was reported by command "brctl show" as xen bridge
with virtual interface peth2 attached.
Create installation SNV84 DomU profile:-

# cat SNV84.install

name = "Solaris84pvm"
vcpus = 1
memory = "1024"
kernel = "/usr/lib/xen-solaris/unix-84"
ramdisk = "/usr/lib/xen-solaris/x86.miniroot-84"
extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom"
disk = ['file:/usr/lib/xen-solaris/snv84.iso,6:cdrom,r','phy:/dev/sdb7,0,w']
vif = ['bridge=eth2']
on_shutdown = "destroy"
on_reboot = "destroy"
on_crash = "destroy"

# xm create -c SNV84.install

Runtime profile:-

name = "Solaris84pvm"
vcpus = 1
memory = "1024"
kernel = "/usr/lib/xen-solaris/unix-84"
ramdisk = "/usr/lib/xen-solaris/x86.miniroot-84"
extra = "/platform/i86xpv/kernel/amd64/unix"
disk = ['phy:/dev/sdb7,0,w']
vif = ['bridge=eth2']
on_shutdown = "destroy"
on_reboot = "destroy"
on_crash = "destroy"

Runtime snapshots:-

Starting up Oracle instance on DomU:-

Launching browser at DomU to Oracle consoles:-

Launching browser at Dom0 to Oracle consoles, running at DomU :-

Jurgen Keil pointed my attention to CR 6631419 at
This CR contains workaround bringing Gnome Desktop back to life.
Run as root:-

for d in /usr/share/icons/*;
[-d $d ] && gtk-update-icon-cache --force $d;

Runtime snapshots for SNV84 DomU at Xen 3.2 CentOS 5.1 Dom0 with Gnome desktop:-