]> git.proxmox.com Git - pve-kernel-3.10.0.git/blob - README
update intel network drivers
[pve-kernel-3.10.0.git] / README
1 KERNEL SOURCE:
2 ==============
3
4 We use the CENTOS7/RHEL7 kernel sources, available from:
5
6 http://vault.centos.org/
7
8 or
9
10 http://oss.oracle.com/ol7/SRPMS-updates/
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 - include latest e1000e driver from intel/sourceforge
21
22 include latest Broadcom bnx2 drivers: http://driverdownloads.qlogic.com/
23
24 * original file linux-7.11.05.zip contains
25 netxtreme2-7.11.05.tar.gz (added to repository)
26
27 - include latest Adaptec aacraid driver
28
29 * http://download.adaptec.com/raid/aac/linux/aacraid-linux-src-1.2.1-40300.tgz
30
31 - include latest ARECA RAID drivers
32
33 * http://www.areca.com.tw/support/s_linux/linux.htm
34
35 - include native OpenZFS filesystem kernel modules for Linux
36
37 * https://github.com/zfsonlinux/
38
39 For licensing questions, see: http://open-zfs.org/wiki/Talk:FAQ
40
41 - include latest HPSA driver (HP Smart Array)
42
43 * http://sourceforge.net/projects/cciss/
44
45 - include latest DRBD 9 driver, see http://drbd.linbit.com/home/what-is-drbd/
46
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 pve-kernel-3.10.0
59
60 We use 'find-firmware.pl' to extract lists of required firmeware
61 files. The script 'assemble-firmware.pl' is used to read those lists
62 and copy the files from various source directory into a target
63 directory.
64
65 We do not include firmeware for some wireless HW when there is a
66 separate debian package for that, for example:
67
68 zd1211-firmware
69 atmel-firmware
70 bluez-firmware
71
72
73 PATCHES:
74 --------
75
76 bridge-patch.diff: Avoid bridge problems with changing MAC
77 see also: http://forum.openvz.org/index.php?t=msg&th=5291
78
79 Behaviour after 2.6.27 has changed slighly - after setting mac address
80 of bridge device, then address won't change. So we could omit
81 that patch, requiring to set hwaddress in /etc/network/interfaces.
82
83
84 Additional information
85 ----------------------
86
87 We use the default configuration provided by RHEL, and apply
88 the following modification:
89
90 see config-3.10.0.diff
91
92 - enable CONFIG_CEPH_FS=m (request from user)
93
94 - enable common CONFIG_BLK_DEV_XXX to avoid hardware detection
95 problems (udev, undate-initramfs hav serious problems without that)
96
97 CONFIG_BLK_DEV_SD=y
98 CONFIG_BLK_DEV_SR=y
99 CONFIG_BLK_DEV_DM=y
100
101 - compile NBD and RBD modules
102 CONFIG_BLK_DEV_NBD=m
103 CONFIG_BLK_DEV_RBD=m
104
105 - set LOOP_MIN_COUNT to 8 (debian defaults)
106 CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
107
108 - disable module signatures (CONFIG_MODULE_SIG)
109
110 - enable IBM JFS file system
111
112 This is disabled in RHEL kernel for no real reason, so we enable
113 it as requested by users (bug #64)
114
115 - enable apple HFS and HFSPLUS
116
117 This is disabled in RHEL kernel for no real reason, so we enable
118 it as requested by users
119
120 - enable CONFIG_BCACHE=m (requested by user)
121
122 - enable CONFIG_BRIDGE=y
123
124 Else we get warnings on boot, that
125 net.bridge.bridge-nf-call-iptables is an unknown key
126
127 - disable CONFIG_DEFAULT_SECURITY_SELINUX
128
129 Use same SELINUX config as debian kernels (CONFIG_DEFAULT_SECURITY_DAC=y)
130
131 - set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
132
133 because if not set, it can give some dynamic memory or cpu frequencies
134 change, and vms can crash (mainly windows guest).
135
136 see http://forum.proxmox.com/threads/18238-Windows-7-x64-VMs-crashing-randomly-during-process-termination?p=93273#post93273
137
138 - set CONFIG_CC_STACKPROTECTOR_REGULAR=y
139
140 gcc on debian wheezy does not supportCONFIG_CC_STACKPROTECTOR_STRONG
141
142 # Note: enable now for testing
143 #- disable CONFIG_BRIDGE_IGMP_SNOOPING
144 #
145 # To avoid problems with multicasting. Various users reported
146 # multipath problems, which can be avoided by turning off IGMP
147 # snooping.
148
149 # deadline is default anyways now
150 #- use 'deadline' as default scheduler
151 #
152 # This is the suggested setting for KVM. We also measure bad fsync
153 # performance with ext4 and cfq.
154
155 Testing final kernel with kvm
156 -----------------------------
157
158 kvm -kernel data/boot/vmlinuz-3.10.0-2-pve -initrd initrd.img-3.10.0-2-pve -append "vga=791 video=vesafb:ywrap,mtrr" /dev/zero
159