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