Thursday, March 13, 2008


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 http://xenbits.xensource.com/xen-3.2-testing.hg
# 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., 2.6.18.8-xen)
Generate the module dependency list and map files



# /sbin/depmod 2.6.18.8-xen



Create the Xen initial ramdisk image



# /sbin/mkinitrd /boot/initrd-2.6.18.8-xen.img   2.6.18.8-xen



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  (2.6.18.8-xen) 
root (hd1,4) 
kernel /xen-3.2.gz 
module /vmlinuz-2.6.18.8-xen ro root=/dev/VolGroup01/LogVol00 rhgb quiet 
module /initrd-2.6.18.8-xen.img



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']
root="/dev/dsk/c0d0s0"
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 :-

















P.S.
Jurgen Keil pointed my attention to CR 6631419 at opensolaris.org:-
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6631419
This CR contains workaround bringing Gnome Desktop back to life.
Run as root:-



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





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









Posted by at