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