Dinsdag 9/10/2007

10h - 13h

• Getting started in TestLab
• Got useraccount and sambashare
• Read some of the howtos and sniffed a bit around on the intranet page
• Setup VPN acount on laptop
• Had to reboot the two testmachines... (Forgot that... thought you needed vpn for this)
• Ping towards two machines works
• No logindetails so a bare install is needed
• Read some documentation on how to install via fai: pxe_netboot_setup_howto.txt
• installed first machine with a ubuntu-64-server via pxe boot
• installed with lvm
• network is not working yet. No dhcp ? Do I need to configure it manual?
• https://www.atlantis.ugent.be/tech_info/Administration/ip_subnets.txt -- info over subnets en gateway

testnet(control)
range 10.10.0.0/17		10.10.10.12 (typhon)	.test			vlan id 6
		(broadcast:.127.255, mask 255.255.128.0)

14h15 - 17h

• added the network details into /etc/network/interfaces static configured

auto eth2
iface eth2 inet static
        address 10.10.3.164
        netmask 255.255.128.0
        broadcast 10.10.127.255
        gateway 10.10.10.12

• remark: the interface is called eth2 but it is the one attached to the motherboard so should be eth0? So marks on the network interfaces are not correct anymore.
• aptitude install ssh : Now I have remote access.
• I use aptitude. People taught me it is better in handling dependencies than apt-get AptitudeOrApt
• I will install other machine later
• Find hardware details of machine
• changed /etc/apt/sources.list with belnet mirrors and umcommented universe repository
• Used this generator http://www.ubuntu-nl.org/source-o-matic/
• aptitude update to get new package info
• aptitude search hwinfo
• aptitude install hwinfo
• PROBLEM: IP address changes all the time from the manual entered ip 10.10.3.164 to 10.10.10.26 Dont know why asked admins
• Hardware info via hwinfo
• Processor:

 Hardware Class: cpu
  Arch: X86-64
  Vendor: "AuthenticAMD"
  Model: 15.79.2 "AMD Athlon(tm) 64 Processor 3200+"
  Features: fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,
fxsr,sse,sse2,syscall,nx,mmxext,fxsr_opt,lm,3dnowext,3dnow,pni,cx16,lahf_lm
  Clock: 2009 MHz
  Cache: 512 kb
  Config Status: cfg=new, avail=yes, need=no, active=unknown

• of cat /proc/cpuinfo

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 79
model name      : AMD Athlon(tm) 64 Processor 3200+
stepping        : 2
cpu MHz         : 2009.173
cache size      : 512 KB
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16 lahf_lm
bogomips        : 4024.49
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc

• http://en.wikipedia.org/wiki/List_of_AMD_Athlon_64_microprocessors
• I dont know which one it is exactly but it is a 3200+ but is a single core.
• It is a xen compatible cpu http://wiki.xensource.com/xenwiki/HVM_Compatible_Processors ==> not correct !
• x86 virtualization : http://en.wikipedia.org/wiki/X86_virtualization

 AMD-V is present in all K8 AMD (Athlon 64) processors from stepping "F" and all newer 
processors support AMD-V technology. This applies for all current Socket AM2 and Socket F 
processors. On Linux, AMD processors supporting virtualization have a svm flag in the 
special file /proc/cpuinfo

• So NO virtualization support which means no possibility to virtualize a Windows machine.
• Start reading book Virtualization with Xen