README

   1 KERNEL SOURCE:
   2 ==============
   3
   4 We use the OpenVZ Kernel sources, available from:
   5
   6 http://download.openvz.org/kernel/branches/rhel6-2.6.32/
   7
   8
   9 Additional/Updated Modules:
  10 ---------------------------
  11
  12 - we use bootsplash to display the boot logo.
  13
  14 - include latest AoE driver (http://support.coraid.com/support/linux)
  15
  16 - include latest ixgbe driver from intel/sourceforge
  17
  18 - include latest igb driver from intel/sourceforge
  19
  20 - include latest e1000e driver from intel/sourceforge
  21
  22 - include latest Broadcom bnx2 drivers: http://driverdownloads.qlogic.com/
  23
  24   * original file linux-7.10.14.zip contains
  25     netxtreme2-7.10.14.tar.gz (added to repository)
  26
  27 - include latest Adaptec aacraid driver
  28
  29   * http://download.adaptec.com/raid/aac/linux/aacraid-linux-src-1.2.1-40700.tgz
  30
  31 - include latest megaraid_sas driver
  32
  33   * http://www.lsi.com/support/pages/download-search.aspx
  34   * download "6.703.11.00-2_MR Linux_Driver.zip"
  35
  36   (extract source file megaraid_sas-06.703.11.00-src.tar.gz)
  37
  38 - include Highpoint RocketRAID 272X driver
  39
  40   * http://www.highpoint-tech.com/BIOS_Driver/rr272x_1x/linux_1.5/RR272x_1x-Linux-Src-v1.5-130325-0732.tar.gz
  41
  42 - include latest ARECA RAID drivers
  43
  44   * http://www.areca.com.tw/support/s_linux/linux.htm
  45
  46 FIRMWARE:
  47 =========
  48
  49 We create our own firmware package, which includes the firmware for
  50 all proxmox-ve kernels. So far this include
  51
  52 pve-kernel-2.6.18
  53 pve-kernel-2.6.24
  54 pve-kernel-2.6.32
  55 pve-kernel-2.6.35
  56
  57 We use 'find-firmware.pl' to extract lists of required firmeware
  58 files.  The script 'assemble-firmware.pl' is used to read those lists
  59 and copy the files from various source directory into a target
  60 directory.
  61
  62 We do not include firmeware for some wireless HW when there is a
  63 separate debian package for that, for example:
  64
  65 zd1211-firmware
  66 atmel-firmware
  67 bluez-firmware
  68
  69
  70 PATCHES:
  71 --------
  72
  73  bootsplash-3.1.9-2.6.31-rh.patch: bootsplash patch
  74
  75  bridge-patch.diff: Avoid bridge problems with changing MAC
  76   see also: http://forum.openvz.org/index.php?t=msg&th=5291
  77
  78   Behaviour after 2.6.27 has changed slighly - after setting mac address
  79   of bridge device, then address won't change. So we could omit
  80   that patch, requiring to set hwaddress in /etc/network/interfaces.
  81
  82
  83 Additional information
  84 ----------------------
  85
  86 We use the default configuration provided by openvz, and apply
  87 the following modification:
  88
  89 see config-2.6.32.diff
  90
  91 - enable bootsplash
  92         CONFIG_FB_VESA=y
  93         CONFIG_FRAMEBUFFER_CONSOLE=Y
  94         CONFIG_BOOTSPLASH=y
  95
  96 - disable CONFIG_DEBUG_INFO
  97
  98 - disable CONFIG_PRINTK_TIME
  99
 100 - enable common CONFIG_BLK_DEV_XXX to avoid hardware detection
 101   problems (udev, undate-initramfs hav serious problems without that)
 102
 103          CONFIG_BLK_DEV_SD=y
 104          CONFIG_BLK_DEV_SR=y
 105          CONFIG_BLK_DEV_DM=y
 106
 107 - disable module signatures (CONFIG_MODULE_SIG, CONFIG_CRYPTO_SIGNATURE)
 108
 109 - enable usbip (this is also enable on debian kernels)
 110
 111          CONFIG_USB_IP_COMMON=m
 112          CONFIG_USB_IP_VHCI_HCD=m
 113          CONFIG_USB_IP_HOST=m
 114
 115 - enable IBM JFS file system
 116
 117   This is disabled in RHEL kernel for no real reason, so we enable
 118   it as requested by users (bug #64)
 119
 120 - enable apple HFS and HFSPLUS
 121
 122   This is disabled in RHEL kernel for no real reason, so we enable
 123   it as requested by users
 124
 125 - enable CONFIG_BRIDGE=y
 126
 127   Else we get warnings on boot, that
 128   net.bridge.bridge-nf-call-iptables is an unknown key
 129
 130 - disable CONFIG_BRIDGE_IGMP_SNOOPING
 131
 132   To avoid problems with multicasting. Various users reported
 133   multipath problems, which can be avoided by turning off IGMP
 134   snooping.
 135
 136 - use 'deadline' as default scheduler
 137
 138   This is the suggested setting for KVM. We also measure bad fsync
 139   performance with ext4 and cfq.
 140
 141 - set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
 142
 143   because if not set, it can give some dynamic memory or cpu frequencies
 144   change, and vms can crash (mainly windows guest).
 145
 146   see http://forum.proxmox.com/threads/18238-Windows-7-x64-VMs-crashing-randomly-during-process-termination?p=93273#post93273
 147
 148 Testing final kernel with kvm
 149 -----------------------------
 150
 151 kvm -kernel data/boot/vmlinuz-2.6.32-6-pve -initrd initrd.img-2.6.32-6-pve -append "vga=791 video=vesafb:ywrap,mtrr splash=silent" /dev/zero
 152