Hello,
I noted this problem on build 98 of 2008.11 and have recently verified it
exists in the production release as well.
I have installed 2008.11 as a guest under Xen. If you make an exact
block-level copy of the image and attach the copy as a disk on the original OS,
zpool import does not
Thanks for all of your input. I intalled 2008.11 build 98 as an HVM guest
under Xen:
If you make a block-level copy of the boot pool and attach it as a disk on the
original VM, "zpool import" does not recognize it. If you attach a non-root
pool as a disk, "zpool import" does recognize it. S
I am running OpenSolaris 2008.05 as a PV guest under Xen. If you import the
bootable root pool of a VM into another Solaris VM, the root pool is no longer
bootable.
It is related to the device associated to the pool, which is originally c4d0s0,
but on import (-f) becomes c0d2s0 in this case.
I am using OpenSolaris 2008.05. If I do "zpool create -R /altroot mypool c0d3"
then "zfs get mountpoint mypool" shows the value as "/altroot" rather then
/altroot/mypool".
If you then do "zpool export mypool" followed by "zpool import mypool", you get:
cannot mount 'mypool': No such file or di