Hi,
This sort of thing has always been difficult to do with Solaris due
to our use of device paths-- it's not just the root path that's the
problem-- the entire /dev needs to be changed to refer to device nodes
that actually exist on the booted system. /etc/path_to_inst also
includes state tied to the physical machine. The metadata that is in
the root pool cannot even help you either because the device path and
devid stored in there won't match when you move the image to a machine
the way you have done. Solaris was never designed to be transplanted
like this. The best advice would be to do a backup of essential files
and restore them to the other machine after the installer has completed.
--S
On Apr 24, 2010, at 4:34 PM, Andrej Podzimek <[email protected]>
wrote:
Hello,
just a piece of bad news on this topic. :-(
The kernel attempts to find the root filesystem here:
/p...@0,0/pci17aa,2...@1f,2/d...@0,0:a
The virtual machine exposes the disk as an IDE drive:
/p...@0,0/pci-...@1,1/i...@0/c...@0,0
How could I tell the kernel to use IDE instead of SATA when running
on
the VM? Should I use VirtualBox instead and emulate AHCI there?
I have just tried VirtualBox with AHCI, but this did not help. Still
the same problem. This means that the root device name must be
stored somewhere in the boot ramdisk image.
Andrej
_______________________________________________
install-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/install-discuss
_______________________________________________
install-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/install-discuss
