Stephen Quintero
2008-Sep-26 20:38 UTC
zpool import of bootable root pool renders it unbootable
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. Afterwards, booting the original image results in a kernel panic because, I think, zfs_mountroot() cannot mount the root path (which is evidently now wrong). I this fixable? How does one "mount" (import) a bootable zpool without wrecking it? This is something that is commonly done under virtualization platforms, e.g., to manage the contents of a VM from another VM, or to perform a file-system level copy of the contents of a VM to another device. Any insight would be appreciated. -- This message posted from opensolaris.org
Seemingly Similar Threads
- 8.2.2004 Latest yum update renders machine unbootable
- 8.2.2004 Latest yum update renders machine unbootable
- 8.2.2004 Latest yum update renders machine unbootable
- 8.2.2004 Latest yum update renders machine unbootable
- 8.2.2004 Latest yum update renders machine unbootable