README

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