Setup Solaris Nevada (build 117) PV DomU at Xen 3.4.1 Ubuntu 9.04 Dom0 via backport CS 19889 libfsimage: Support for zfs version 16

Actually, CS 19889 is in Xen 3.5 Unstable. However, attempt to install mentioned DomU at Xen 3.5 Dom0 via standard pygrub profile:-

root@ServerXen341:/home/boris/nevada# cat snv117.install
name = 'Solaris117PV'
memory = '2048'
disk = [ 'phy:/dev/loop0,6:cdrom,r','phy:/dev/sdb3,0,w']
vif = [ 'bridge = eth1' ]
bootloader = '/usr/local/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'
root@ServerXen341:/home/boris/nevada# xm create -c snv117.install

aborts with message cannot find kernel “/boot/platform/i86xpv/kernel/amd64/unix”. Setup bellow has been tested with 2.6.30.1 xenified (aka Suse) kernel and 2.6.31-rc1 pvops enabled kernel been built via rebase/master branch of Jeremy Fitzhardinge git repository. The root cause of the problem is ZFS v.16 utilized by SNV_117 DomU for it’s image device unsupported by Xen 3.4.1. Place “raw” content of CS 19889 into file /usr/src/zfs16.patch1.
Next step :-

# cd /usr/src
# hg clone http://xenbits.xensource.com/xen-3.4-testing.hg
# cd xen-3.4-testing.hg
*******************************
Set in Config.mk
PYTHON = python
PYTHON_PREFIX_ARG =
*******************************
# patch -p1 -s -i ../zfs16.patch1
# make xen
# make tools
# make stubdom
# make install-xen
# make install-tools
# make install-stubdom

Modify corresponding Grub entry and reboot Xen Host.
Install SNV_117 DomU via profile above. To be sure install would be OK use only primary partitions as image devices for SNV_117 DomU (ZFS based) or the first one in extended partion on x86 architecture.
Symptom of wrong partition choice could be message showing up when attempt to load via standard pygrub profile :-

NOTICE: zfs_parse_bootfs: error 2
Cannot mount root on rpool/57 fstype zfs
panic[cpu0]/thread=fffffffffbc60c20: vfs_mountroot: cannot mount root
fffffffffbc94a00 genunix:vfs_mountroot+350 ()
fffffffffbc94a30 genunix:main+f0 ()
fffffffffbc94a40 unix:_locore_start+80 ()
skipping system dump - no dump device configured
rebooting...

VNC Setup on SNV_117 DomU is the same as on OSOL 2009.06 DomU.

cat /etc/X11/gdm/custom.conf
# GDM Custom Configuration file.
# overrides: /usr/share/gdm/defaults.conf
[daemon]
RemoteGreeter=/usr/lib/gdmgreeter
[security]
DisallowTCP=false
# AllowRoot=true
# AllowRemoteRoot=true
[xdmcp]
Enable=true
[gui]
[greeter]
[chooser]
[debug]
[servers]

Services restart:-

svcadm disable xvnc-inetd gdm
svcadm enable xvnc-inetd gdm

Vinagre remote console :-





Standard VNC console :-

---

Possibly related posts: (automatically generated)

• Setup OpenSolaris 1002-127 PV DomU at Xen 3.4.2 & Libvirt 0.7.1-15 (2.6.31….
• Setup Debian Lenny PV & HVM DomUs (64-bit) sharing same image device at Xen…
• Ubuntu 9.10 Server PV & HVM DomUs sharing same image at Sun xVM 3.4.2 on to…
• Easy Virtualization using Xen Hypervisor and Cent OS