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 [email protected]
