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