xen discuss - Jun 2008 - OpenSolaris domU hangs at xen create after package upgrade

Hi,

I created OpenSolaris domU on Fedora 8 dom0 using OpenSolaris 2008-05 CD,
everything works fine after init bootup: I can login, run firefox ....

After domU is created and running, I decided to upgrade packages using System
>Administration > Package Manager, then shutdown.

At last, I did a start again by
#xm create -c pv.py

It hangs with message:
Using config file "./pv.py".
Started domain opensolaris
v3.1.3 chgset ''unavailable''
SunOS Release 5.11 Version snv_86 32-bit
Copyright 1983-2008 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
WARNING: file system ''ctfs'' version mismatch
WARNING: Cannot mount /system/contract
/kernel/fs/procfs: undefined symbol ''schedctl_set_cidpri''
WARNING: mod_load: cannot load module ''procfs''
WARNING: Cannot mount /proc
WARNING: file system ''mntfs'' version mismatch
WARNING: Cannot mount /etc/mnttab
WARNING: file system ''tmpfs'' version mismatch
WARNING: Cannot mount /etc/svc/volatile
WARNING: file system ''objfs'' version mismatch
WARNING: Cannot mount /system/object
WARNING: file system ''sharefs'' version mismatch
WARNING: Cannot mount /etc/dfs/sharetab
/kernel/fs/procfs: undefined symbol ''schedctl_set_cidpri''
WARNING: mod_load: cannot load module ''procfs''
WARNING: file system ''sockfs'' version mismatch
/kernel/fs/procfs: undefined symbol ''schedctl_set_cidpri''

Any idea how it happens and what I can do ?

This is my pv.py
name = "opensolaris"
vcpus = 1
memory = "512"
kernel = ''/opt/img/os-08-05/unix''
ramdisk = ''/opt/img/os-08-05/boot_archive''
extra = ''/platform/i86xpv/kernel/unix -B zfs-bootfs=rpool/27''
#extra = ''/platform/i86xpv/kernel/unix''
disk = [ ''file:/opt/img/os-08-05/solaris.img,0,w'']
#root= ''/dev/dsk/c0t0d0''
vif = [''mac=00:16:3e:70:01:01'']
on_shutdown = "destroy"
on_reboot = "restart"
on_crash = "destroy"

The fedora 8 system xen packages are:
kernel-xen-2.6.21.7-3.fc8
xen-libs-3.1.2-2.fc8
xen-3.1.2-2.fc8
kernel-xen-devel-2.6.21.7-3.fc8

[root@core xen]# uname -r
2.6.21.7-3.fc8xen
 
 
This message posted from opensolaris.org

On 17 Jun 2008, at 4:54am, Jason Zhang wrote:
> I created OpenSolaris domU on Fedora 8 dom0 using OpenSolaris  
> 2008-05 CD, everything works fine after init bootup: I can login,  
> run firefox ....
>
> After domU is created and running, I decided to upgrade packages  
> using System >Administration > Package Manager, then shutdown.
This probably updated the kernel and the boot archive. You need to  
extract those again so that dom0 can load them when building the domain.
> kernel = ''/opt/img/os-08-05/unix''
> ramdisk = ''/opt/img/os-08-05/boot_archive''
> extra = ''/platform/i86xpv/kernel/unix -B
zfs-bootfs=rpool/27''
i.e. these files need to be updated to correspond to those within the  
domain.

but how ...

I tried use live CD boot again, but have no clue how to mount my disk back, I
can do

#make /b
#zpool --import /b -f rpool

but under /b, I only found /b/ROOT, /b/export, /b/opt, nothing about
/platform/...

--Jason
 
 
This message posted from opensolaris.org

I managed to get boot_archive and kernel(unix) out of the image and put in dom0,
but it is still not coming up even use the ones copied out.

Looked back some threads in this forum, look like zfs-bootfs=rpool/27 may be the
cause. Who know about what rpool/27 is and how it is determined.

Thanks
 
 
This message posted from opensolaris.org

> I managed to get boot_archive and kernel(unix) out of
> the image and put in dom0, but it is still not coming
> up even use the ones copied out.
What kind of error messages does it report?

Does the kernel now announce itself with snv_90:

    SunOS Release 5.11 Version snv_90 32-bit

snv_90 instead of snv_86?
> Looked back some threads in this forum, look like
> zfs-bootfs=rpool/27 may be the cause. Who know about
> what rpool/27 is and how it is determined.
"rpool" is the zpool''s name and is the expected name
for OpenSolaris 2008.05.

"27" should the the zfs filesystem id of the zfs root filesystem.
For OpenSolaris 2008.05, that was rpool/ROOT/opensolaris,
and running "zdb rpool/ROOT/opensolaris" shows the  ID 27.

Unfortunately, you can''t use "-B
zfs-bootfs=rpool/ROOT/opensolaris"
in the domain''s config file; you have to use the numeric zfs ID
instead.

As far as I know, the OpenSolaris update to snv_90 creates
a new cloned zfs filesystem for root, so I assume the ID
for the root filesystem will change.
 
 
This message posted from opensolaris.org

If I use the boot_archive copied out from img, the boot process die quickly:

[root@core xen]# xm create -c pv.py
Using config file "./pv.py".
Started domain opensolaris
                          not found: spa_boot_init
not found: hvmboot_rootconf
do_relocations: /kernel/genunix do_relocate failed
krtld: error during initial load/link phase

krtld could neither locate nor resolve symbols for:
    /platform/i86xpv/kernel/unix
in the boot archive. Please verify that this file
matches what is found in the boot archive.
You may need to boot using the Solaris failsafe to fix this.
Unable to boot
Press any key to reboot.
Resetting...


If I am using old boot_archive

Using config file "./pv-1.py".
Started domain opensolaris
                          v3.1.3 chgset ''unavailable''
SunOS Release 5.11 Version snv_86 32-bit
Copyright 1983-2008 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
WARNING: file system ''ctfs'' version mismatch
WARNING: Cannot mount /system/contract
/kernel/fs/procfs: undefined symbol ''schedctl_set_cidpri''
WARNING: mod_load: cannot load module ''procfs''
WARNING: Cannot mount /proc
WARNING: file system ''mntfs'' version mismatch
WARNING: Cannot mount /etc/mnttab
WARNING: file system ''tmpfs'' version mismatch
 
 
This message posted from opensolaris.org

Jürgen Keil wrote:
>> I managed to get boot_archive and kernel(unix) out of
>> the image and put in dom0, but it is still not coming
>> up even use the ones copied out.
> 
> What kind of error messages does it report?
> 
> Does the kernel now announce itself with snv_90:
> 
>     SunOS Release 5.11 Version snv_90 32-bit
> 
> snv_90 instead of snv_86?
> 
>> Looked back some threads in this forum, look like
>> zfs-bootfs=rpool/27 may be the cause. Who know about
>> what rpool/27 is and how it is determined.
> 
> "rpool" is the zpool's name and is the expected name
> for OpenSolaris 2008.05.
> 
> "27" should the the zfs filesystem id of the zfs root filesystem.
> For OpenSolaris 2008.05, that was rpool/ROOT/opensolaris,
> and running "zdb rpool/ROOT/opensolaris" shows the  ID 27.
> 
> Unfortunately, you can't use "-B
zfs-bootfs=rpool/ROOT/opensolaris"
> in the domain's config file; you have to use the numeric zfs ID
> instead.
> 
> As far as I know, the OpenSolaris update to snv_90 creates
> a new cloned zfs filesystem for root, so I assume the ID
> for the root filesystem will change.
The cloned root filesystem should be rpool/ROOT/opensolaris-1.

When you have the pool imported when running on the LiveCD, you can
verify this by doing:
zpool get all <poolname> | grep bootfs

Using zdb you can find the number associated with the clone:
zdb -vvv <poolname> | grep bootfs

This is the number to place into
   -B zfs-bootfs=rpool/<number>

Susan
_______________________________________________
xen-discuss mailing list
xen-discuss@opensolaris.org

Finally, GIVE UP,
I found this FAQ item in zfs
http://opensolaris.org/os/community/zfs/boot/zfsbootFAQ/#mixoses

the zfs boot feature cannot upgrade OS-08-05 to latest (snv_90).

I would suggest everyone get with snv_90 as a start, not OS-08-05 anymore!
 
 
This message posted from opensolaris.org