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 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
# cd xen-3.4-testing.hg
Set in
PYTHON = python
# 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

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
# AllowRoot=true
# AllowRemoteRoot=true

Services restart:-

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

Vinagre remote console :-

Standard VNC console :-

4 Responses to 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

  1. Sam says:

    I have RHEL 5.4 and am trying to install Solaris 10 05/2009 drop (latest).

    I am having a very hard time installing a VM instance of Solaris on Redhat. I believe I am running xen 3.0 (can’t quite confirm) and hence the installation hangs after I pass the Grub screen.

    Any specifics how to solve this problem?

  2. dbaxps says:

    Run “xm list” to make sure what is Solaris HVM status after
    Grub entry selection. Which one output you see ?

    S10HVM r—–
    S10HVM -p—-
    S10HVM -b—-

  3. Andy says:

    I’m trying to get a Solaris DomU up on Oracle VM. Oracle VM is basically just Redhat with pre-installed Xen, but I keep getting an ‘invalid kernel’ error. Specifically,

    Error: (2, ‘Invalid kernel’, ‘elf_xen_note_check: ERROR: Will only load images built for the generic loader or Linux images’)

    This is when trying to use any of the kernels on the Solaris install disk. Any idea how to get past this?

  4. Young Money says:

    Cool blog you have here. I just heard that new Curren$y track and your site came up.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: