On Wed, Feb 10, 2010 at 02:52:21PM -0800, Alan Landucci-Ruiz wrote: > I don't think it's the problem with the vbox driver, but it's worth trying.
Me either. I just successfully booted 132 on one of the problem machines, without removing vbox. I went back to my older 128b BE, and ran the image-update from there. This is a pain, because some config and machine state since then will be lost, but evidently that includes some bad config as well as good. One guess: the iscsi initiator, which I installed after upgrading 128b to 130, and which therefore isn't present in my new, working 132 BE. It gave me much trouble with not starting properly under 130 anyway. I haven't tried installing that again over b132 - later. The other problem machine has no older BE for me to try this from; it is a netbook and has a very small SSD for rpool, so older BE's get destroyed relatively quickly to save space. Sadly, it doesn't have the iscsi initiator installed either. -- Dan.
pgpGYqDnxtPUV.pgp
Description: PGP signature
_______________________________________________ opensolaris-discuss mailing list [email protected]
