Homework 2: Software -- VM Installation notes

thingsplaneΔιακομιστές

9 Δεκ 2013 (πριν από 3 χρόνια και 6 μήνες)

93 εμφανίσεις

Fundamentals of System Administration

Harvard Extension School

Fall 2008


Page
1
of
4




Homework 2: Software

--

VM
Installation notes


CentOS: Installer won’
t detect the local disk


It seems that the CentOS installer occasionally has problems detecting the VMWare
virtual disk. If you run into this issue, simply exit the install and try again. If the problem
persists, change your VMWare virtual disk from SCSI
to IDE.



Solaris 10:
A
Few S
teps that
S
tray
from the Standard I
nstall


On the

NFSv4 Domain Name

screen, specifiy a name of

vanilla

.


On the

DHCP for pcn0

screen, select DHCP:



On the

Name Service

screen, select

None

.



On the

Select Disks

page, hit F4.

Fundamentals of System Administration

Harvard Extension School

Fall 2008


Page
2
of
4






On the

Customize fdisk Partitions

page, highlight partition 1 and hit enter.



On the

fdisk Partition Size

screen, select the whole virtual disk.




Solaris 10:
Slow to
Enter GUI


If you see a CLI screen prompting
you to login to the console, just wait. The GUI
sometimes takes a long time to load. You can mitigate this by increasing the amount of
RAM allocated to the guest VM.


Fundamentals of System Administration

Harvard Extension School

Fall 2008


Page
3
of
4




Solaris 10:
64
-
bit Error Message
in VMWare


When the Solaris 10 guest detects the host processor's 64
-
bit capability during
in
stallation, it attempts to enter longmode, and Workstation displays an error message
indicating that you do not have a supported 64
-
bit processor. You may be able to work
around this problem by suppressing the longmode feature. Try adding the following lin
e
to the guest virtual machine's configuration (.vmx) file:

monitor_control.disable_longmode  1


Once you have successfully installed Solaris 10 in 32
-
bit mode, VMware recommends
that you remove the line from the configuration file, since this setting mig
ht cause
problems with some applications. To force Solaris 10 to boot in 32
-
bit mode on a 64
-
bit
host, execute the following command from a command line prompt within the guest:

eeprom boot
-
filekernel/unix

This command requires superuser privileges.


Note
: If you upgrade the guest operating system (for example, from Solaris 10 Upgrade
1 to Solaris 10 Upgrade 2), you need to re
-
execute the eeprom command because the
entry is automatically removed on upgrade.


The Sun Web site provides more information on th
is issue. Go to

docs.sun.com/app/docs/doc/817
-
1985/6mhm8o5nb?aview.


(Copied from:
http://kb.vmware.com/selfservice/microsites/search.do?langua
geen_US&cmddisplayKC&externalId1975
)



Solaris 10:
Unknown Hostname
Error Message


It is easy to miss the name configuration when
you are
following the Solaris setup. If
you get a hostname error on first boot, don’t panic! This happens because Sola
ris
expects to be told its
nodename from the DHCP server. B
ut most
DHCP servers
(like
the one in VMWare) don’t expect to serve this information.
To
resolve the problem:


1.

Create the file /etc/nodename

2.

Edit nodename; it’s contents should be: vanilla

3.

Edit
the /etc/hosts file
so that the line beginning with
"127.0.0.1
"
looks like:



127.0.0.1
localhost vanilla



Fundamentals of System Administration

Harvard Extension School

Fall 2008


Page
4
of
4




Solaris 10:
/home Not Writeable


Solaris assumes that you want the /home
directory to be mounted from a remote file
system. Therefore, there are two ways around this problem:


1.

Ignore /home and use /export/home for all of your users’ home directory needs


Or


2.

Stop automounting /home

a.

/etc/init.d/autofs stop

b.

Edit /et
c/auto/master

c.

Comment out any line(s) containing the string

auto_home


d.

/etc/init.d/autofs s
tart