README

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