Solaris Nevada 70 install in Fusion
Sunday Dec 02, 2007
I have finally got some cycles to build a new VM. I am installing Solaris Nevada 70.
For the VM setup I am making the following choices:
- Sun Solaris - Solaris 10 64-bit
- Disk size 12 GB
Next I am shutting down the VM and adding memory. The default gives you 512, Neveda needs 768. I normally run 1024, but decided to try 768 for the install.
The VM has started and I have selected Solaris Express Developer Edition and an interactive install. The gui in 70 pops up right away, and you are asked several quick questions, and then the installer fires off to do its thing. Much better than previous versions of the installer!
My install is finished and time for the reboot. At first blush the VM seems more responsive, than 69A.
The good old registration wizard has popped up. On a side note I tried this a long time ago when it first came out. It never worked. Decided I am going to go through and try to register it today. Asking me for username and password like normally, I know the one I original set up won't work so going to go and register. <sigh> Duplicate account failure. So my old account is in there, and it does not work. Trying a new user name... Different user name did not cut it. Trying a different email address, maybe that is what they are keying off of.
Okay this is getting frustrating. I have used a different user name and email address. And still getting duplicate account error. I have finally made up a username that I have never shared with Sun before, and the registration has succeeded. Good thing I have Keychain, because I am never going to remember what I made up! I have turned Update Manager on. I am sure there is a Sun account number we can use, but I don't have it handy. Just turning it on for security updates.
Next I have installed VMware tools. I always forget the path to the toolkit so posting it here for reference /usr/bin/vmware-toolbox. You technically just have to log out and log back in to get vmware tools to take effect, but I like to reboot. I have upgraded Fusion as well. Don't know if the change was the upgrade to fusion or the upgrade to 70, but I can now put the VM into full screen mode and have it work! The rest of the tools seem to be working as well.
Aggh here is something new. I went to configure the network away from DHCP to a static IP. I have been told I can't do this whole Network Auto-Magic is (NWAM) is enabled. There is also a friendly url to help me out. The initial read is that NWAM takes care of DHCP across multiple interfaces. Allows you to roam seamlessly. That is all well and good, but I I am going to be using this VM as a demo server, and it needs a static IP. The first link leads to a second link which has all the details.
bash-3.00# svcs svc:/network/physical
STATE STIME FMRI
disabled 8:35:49 svc:/network/physical:default
online 8:35:53 svc:/network/physical:nwam
I have nwam on and physical off. Need to get this switched around.
bash-3.00# svcadm disable svc:/network/physical:nwam
bash-3.00# svcadm enable svc:/network/physical:default
bash-3.00# svcs svc:/network/physical
STATE STIME FMRI
disabled 12:22:21 svc:/network/physical:nwam
online 12:22:33 svc:/network/physical:default
Looks like things are changed around. I can start network settings, I can change my settings, but I can't get the interface to plumb up. Going for the old MS reboot.
VM is rebooted. Still no network access. Just noticed had a user error. Had the VM set to NAT, not bridged. Worked great on DHCP, but now needs to be changed to bridged, now that I have a static IP on it. If this setting was correct, the reboot above may not have been necessary. I am not going to back to test it though.
I am up and on the network now, but DNS is not working. My resolv.conf has the proper entries. Looks like I do not have the proper nswitch.conf in place.
bash-3.00# cd /etc/
bash-3.00# mv nsswitch.conf nsswitch.conf.v20071201
bash-3.00# cp nsswitch.dns nsswitch.conf
bash-3.00# svcadm restart svc:/network/physical:default
All is well now! Neveda 70 seems to be a much better performer with Fusion 1.1 than my previous install. Probably a combination of both Solaris and Fusion being updated.
|
|
|
|
Get a newer NV. Build 76 was a flawless install.