projects / pve-kernel-jessie.git / blame
| Commit | Line | Data |
|---|---|---|
| 53e8ba20 DM |
1 | KERNEL SOURCE: |
| 2 | ============== | |
| 3 | ||
| 4 | We currently use the Ubuntu kernel sources, available from: | |
| 5 | ||
| 7edf8ae8 | 6 | https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/wily |
| 519b8ca3 | 7 | |
| 7edf8ae8 | 8 | Ubuntu will maintain those kernels till: |
| 519b8ca3 DM |
9 | |
| 10 | https://wiki.ubuntu.com/Kernel/Dev/ExtendedStable | |
| 7edf8ae8 | 11 | |
| 53e8ba20 DM |
12 | |
| 13 | Additional/Updated Modules: | |
| 14 | --------------------------- | |
| 15 | ||
| 68be0861 DM |
16 | - include latest e1000e driver from intel/sourceforge |
| 17 | ||
| 53e8ba20 DM |
18 | - include latest ixgbe driver from intel/sourceforge |
| 19 | ||
| 7921f784 | 20 | # - include latest igb driver from intel/sourceforge |
| 53e8ba20 | 21 | |
| f1944d56 DM |
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/ | |
| 53e8ba20 DM |
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 | ||
| acea917f DM |
71 | Watchdog blacklist |
| 72 | ------------------ | |
| 73 | ||
| 74 | By default, all watchdog modules are black-listed because it is totally undefined | |
| 75 | which device is actually used for /dev/watchdog. | |
| 76 | We ship this list in /lib/modprobe.d/blacklist_pve-kernel-<VERSION>.conf | |
| 77 | The user typically edit /etc/modules to enable a specific watchdog device. | |
| 53e8ba20 DM |
78 | |
| 79 | Additional information | |
| 80 | ---------------------- | |
| 81 | ||
| 82 | We use the default configuration provided by Ubuntu, and apply | |
| 83 | the following modification: | |
| 84 | ||
| 85 | see Makefile (PVE_CONFIG_OPTS) | |
| 86 | ||
| 87 | - enable CONFIG_CEPH_FS=m (request from user) | |
| 88 | ||
| 89 | - enable common CONFIG_BLK_DEV_XXX to avoid hardware detection | |
| 90 | problems (udev, undate-initramfs hav serious problems without that) | |
| 91 | ||
| 92 | CONFIG_BLK_DEV_SD=y | |
| 93 | CONFIG_BLK_DEV_SR=y | |
| 94 | CONFIG_BLK_DEV_DM=y | |
| 95 | ||
| 96 | - compile NBD and RBD modules | |
| 97 | CONFIG_BLK_DEV_NBD=m | |
| 98 | CONFIG_BLK_DEV_RBD=m | |
| 99 | ||
| 100 | - set LOOP_MIN_COUNT to 8 (debian defaults) | |
| 101 | CONFIG_BLK_DEV_LOOP_MIN_COUNT=8 | |
| 102 | ||
| 103 | - disable module signatures (CONFIG_MODULE_SIG) | |
| 104 | ||
| 105 | - enable IBM JFS file system | |
| 106 | ||
| 107 | This is disabled in RHEL kernel for no real reason, so we enable | |
| 108 | it as requested by users (bug #64) | |
| 109 | ||
| 110 | - enable apple HFS and HFSPLUS | |
| 111 | ||
| 112 | This is disabled in RHEL kernel for no real reason, so we enable | |
| 113 | it as requested by users | |
| 114 | ||
| 115 | - enable CONFIG_BCACHE=m (requested by user) | |
| 116 | ||
| 117 | - enable CONFIG_BRIDGE=y | |
| 118 | ||
| 119 | Else we get warnings on boot, that | |
| 120 | net.bridge.bridge-nf-call-iptables is an unknown key | |
| 121 | ||
| 122 | - enable CONFIG_DEFAULT_SECURITY_APPARMOR | |
| 123 | ||
| 124 | We need this for lxc | |
| 125 | ||
| 126 | - set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y | |
| 127 | ||
| 128 | because if not set, it can give some dynamic memory or cpu frequencies | |
| 129 | change, and vms can crash (mainly windows guest). | |
| 130 | ||
| 131 | see http://forum.proxmox.com/threads/18238-Windows-7-x64-VMs-crashing-randomly-during-process-termination?p=93273#post93273 | |
| 132 | ||
| 133 | - use 'deadline' as default scheduler | |
| 134 | ||
| 135 | This is the suggested setting for KVM. We also measure bad fsync | |
| 136 | performance with ext4 and cfq. | |
| 137 | ||
| feaffad1 DM |
138 | - disable CONFIG_INPUT_EVBUG |
| 139 | ||
| 140 | Module evbug is not blacklisted on debian, so we simply disable it | |
| 141 | to avoid key-event logs (which is a big security problem) | |
| 142 | ||
| 53e8ba20 DM |
143 | Testing final kernel with kvm |
| 144 | ----------------------------- | |
| 145 | ||
| 146 | 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 | |
| 147 |