README

   1 KERNEL SOURCE:
   2 ==============
   3
   4 We currently use the Ubuntu kernel sources, available from:
   5
   6  https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/wily
   7
   8 Ubuntu will maintain those kernels till:
   9
  10  https://wiki.ubuntu.com/Kernel/Dev/ExtendedStable
  11
  12
  13 Additional/Updated Modules:
  14 ---------------------------
  15
  16 - include latest e1000e driver from intel/sourceforge
  17
  18 - include latest ixgbe driver from intel/sourceforge
  19
  20 # - include latest igb driver from intel/sourceforge
  21
  22 # Note: hpsa does not compile with kernel 3.19.8
  23 #- include latest HPSA driver (HP Smart Array)
  24 #
  25 #  * http://sourceforge.net/projects/cciss/
  26
  27 - include native OpenZFS filesystem kernel modules for Linux
  28
  29   * https://github.com/zfsonlinux/
  30
  31   For licensing questions, see: http://open-zfs.org/wiki/Talk:FAQ
  32
  33 - include latest DRBD 9 driver, see http://drbd.linbit.com/home/what-is-drbd/
  34
  35
  36 FIRMWARE:
  37 =========
  38
  39 We create our own firmware package, which includes the firmware for
  40 all proxmox-ve kernels. So far this include
  41
  42 pve-kernel-2.6.18
  43 pve-kernel-2.6.24
  44 pve-kernel-2.6.32
  45 pve-kernel-3.10.0
  46 pve-kernel-3.19.0
  47
  48 We use 'find-firmware.pl' to extract lists of required firmeware
  49 files.  The script 'assemble-firmware.pl' is used to read those lists
  50 and copy the files from various source directory into a target
  51 directory.
  52
  53 We do not include firmeware for some wireless HW when there is a
  54 separate debian package for that, for example:
  55
  56 zd1211-firmware
  57 atmel-firmware
  58 bluez-firmware
  59
  60
  61 PATCHES:
  62 --------
  63
  64  bridge-patch.diff: Avoid bridge problems with changing MAC
  65   see also: http://forum.openvz.org/index.php?t=msg&th=5291
  66
  67   Behaviour after 2.6.27 has changed slighly - after setting mac address
  68   of bridge device, then address won't change. So we could omit
  69   that patch, requiring to set hwaddress in /etc/network/interfaces.
  70
  71
  72 Additional information
  73 ----------------------
  74
  75 We use the default configuration provided by Ubuntu, and apply
  76 the following modification:
  77
  78 see Makefile (PVE_CONFIG_OPTS)
  79
  80 - enable CONFIG_CEPH_FS=m (request from user)
  81
  82 - enable common CONFIG_BLK_DEV_XXX to avoid hardware detection
  83   problems (udev, undate-initramfs hav serious problems without that)
  84
  85          CONFIG_BLK_DEV_SD=y
  86          CONFIG_BLK_DEV_SR=y
  87          CONFIG_BLK_DEV_DM=y
  88
  89 - compile NBD and RBD modules
  90          CONFIG_BLK_DEV_NBD=m
  91          CONFIG_BLK_DEV_RBD=m
  92
  93 - set LOOP_MIN_COUNT to 8 (debian defaults)
  94          CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
  95
  96 - disable module signatures (CONFIG_MODULE_SIG)
  97
  98 - enable IBM JFS file system
  99
 100   This is disabled in RHEL kernel for no real reason, so we enable
 101   it as requested by users (bug #64)
 102
 103 - enable apple HFS and HFSPLUS
 104
 105   This is disabled in RHEL kernel for no real reason, so we enable
 106   it as requested by users
 107
 108 - enable CONFIG_BCACHE=m (requested by user)
 109
 110 - enable CONFIG_BRIDGE=y
 111
 112   Else we get warnings on boot, that
 113   net.bridge.bridge-nf-call-iptables is an unknown key
 114
 115 - enable CONFIG_DEFAULT_SECURITY_APPARMOR
 116
 117   We need this for lxc
 118
 119 - set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
 120
 121   because if not set, it can give some dynamic memory or cpu frequencies
 122   change, and vms can crash (mainly windows guest).
 123
 124   see http://forum.proxmox.com/threads/18238-Windows-7-x64-VMs-crashing-randomly-during-process-termination?p=93273#post93273
 125
 126 - use 'deadline' as default scheduler
 127
 128   This is the suggested setting for KVM. We also measure bad fsync
 129   performance with ext4 and cfq.
 130
 131 - disable CONFIG_INPUT_EVBUG
 132
 133   Module evbug is not blacklisted on debian, so we simply disable it
 134   to avoid key-event logs (which is a big security problem)
 135
 136 Testing final kernel with kvm
 137 -----------------------------
 138
 139 kvm -kernel data/boot/vmlinuz-3.19.8-1-pve -initrd initrd.img-3.19.8-1-pve -append "vga=791 video=vesafb:ywrap,mtrr" /dev/zero
 140