This is a notes page, not really documentation, just stuff for me to remember. Sometimes things will get removed from these pages and turned into real documentation, sometimes not. You might find these notes to come in hand, maybe not. For me, it's just things I don't want to forget.

NIC: AMD PCNET32 “Lance” NIC driver
Ethernet0.virtualDev=“vlance” SCSI: Buslogic/LSI logic SCSI adapter driver

VMware tools:
Klik op de “Install VMWare Tools” menu optie en geef het volgende commando:
vmwtools:\setup.ncf

VMware tools:
Dependencies: gcc/gcc++/(kernel-headers)

ON ESX, first mount the cdrom:
OES3:/media # mount /dev/cdrom /mnt/
mount: block device /dev/cdrom is write-protected, mounting read-only

Zet de vm uit, en zet de cdrom op automatically connect as host device, as auto detect.
mount /dev/cdrom /media/cdrom -o rm

Klik op de “Install VMWare Tools” menu optie en geef het volgende commando's:

cd /tmp
tar zxf /media/VMware\ Tools/vmware-linux-tools.tar.gz
cd /tmp/vmware-tools-distrib
./vmware-install.pl
Run tools: /usr/bin/vmware-toolbox

installeer alles in /usr/local/bin

Open

vi /boot/grub/menu.lst

en verwijder “vga=0x332” uit de linux kernel load line

After you've added a new disk to linux you can discover it by issuing 'rescan-scsi-bus.sh' as root:

# rescan-scsi-bus.sh
Host adapter 0 (mptspi) found.
Scanning SCSI subsystem for new devices
Scanning host 0 channels 0 for  SCSI target IDs  0 1 2 3 4 5 6 7, all LUNs
Scanning for device 0 0 0 0 ...
OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00
      Vendor: VMware   Model: Virtual disk     Rev: 1.0
      Type:   Direct-Access                    ANSI SCSI revision: 02
Scanning for device 0 0 1 0 ...
OLD: Host: scsi0 Channel: 00 Id: 01 Lun: 00
      Vendor: VMware   Model: Virtual disk     Rev: 1.0
      Type:   Direct-Access                    ANSI SCSI revision: 02
Scanning for device 0 0 2 0 ...
NEW: Host: scsi0 Channel: 00 Id: 02 Lun: 00
      Vendor: VMware   Model: Virtual disk     Rev: 1.0
      Type:   Direct-Access                    ANSI SCSI revision: 02
0 new device(s) found.
0 device(s) removed.

It says 0 devices found but the new disk is still discovered and ready for partitioning.

bron

Open ntp.conf en pas de volgende instellingen aan:

vi /etc/ntp.conf
server x.x.x.x prefer
tinker step 0

Stop, synchroniseer en start ntp:

/etc/init.d/ntpd stop
ntpdate x.x.x.x (herhalen tot verschil kleiner is dan 1 seconde)
/etc/init.d/ntpd start
ntpq -p (herhalen tot de reach op 377 staat)

vi /boot/grub/menu.lst
Voeg “clock=pit” toe aan de linux kernel load line
of
vi /etc/lilo.conf
Voeg “clock=pit” toe aan de “append=” line
/sbin/lilo

Zet deze naar 333 of 250

Zet tijdssynchronisatie met de host aan via of de VMware tools of de *.vmx config file.

vi /boot/grub/menu.lst
Voeg “noapic nolapic nosmp” toe aan de linux kernel load line

vi /etc/ntp.conf
server x.x.x.x prefer minpoll 4 maxpoll 6 (getal omzetten naar seconden is kwadrant, dus 4=16 seconden en 6=36 seconden)

Hardwareklok synchroniseren met de systeemklok:

hwclock --systohc

Hardwareklok bekijken:

hwclock --show

Indien het bootscherm te snel gaat, F2 is de toets om in de BIOS/CMOS te komen.

I needed to be able to authenticate through LDAP on a virtual from the production network. Of course, vmware server does not support reverse NAT, so I took my chances on port forwarding… and it worked:
Don't forget to press restart and apply when you've added port forwards.