]> git.proxmox.com Git - pve-kernel-2.6.32.git/blob - README
add zfs copyright info
[pve-kernel-2.6.32.git] / README
1 KERNEL SOURCE:
2 ==============
3
4 We use the OpenVZ Kernel sources, available from:
5
6 http://download.openvz.org/kernel/branches/rhel6-2.6.32/
7
8
9 Additional/Updated Modules:
10 ---------------------------
11
12 - we use bootsplash to display the boot logo.
13
14 - include latest stable OVS openvswitch.ko module
15
16 - include latest AoE driver (http://support.coraid.com/support/linux)
17
18 - include latest ixgbe driver from intel/sourceforge
19
20 - include latest igb driver from intel/sourceforge
21
22 - include latest e1000e driver from intel/sourceforge
23
24 - include latest Broadcom bnx2 drivers: http://driverdownloads.qlogic.com/
25
26 * original file linux-7.11.05.zip contains
27 netxtreme2-7.11.05.tar.gz (added to repository)
28
29 - include latest Adaptec aacraid driver
30
31 * http://download.adaptec.com/raid/aac/linux/aacraid-linux-src-1.2.1-40700.tgz
32
33 - include latest megaraid_sas driver
34
35 * http://www.lsi.com/support/pages/download-search.aspx
36 * download "6.703.11.00-2_MR Linux_Driver.zip"
37
38 (extract source file megaraid_sas-06.703.11.00-src.tar.gz)
39
40 - include Highpoint RocketRAID 272X driver
41
42 * http://www.highpoint-tech.com/BIOS_Driver/rr272x_1x/linux_1.5/RR272x_1x-Linux-Src-v1.5-130325-0732.tar.gz
43
44 - include latest ARECA RAID drivers
45
46 * http://www.areca.com.tw/support/s_linux/linux.htm
47
48 - include native OpenZFS filesystem kernel modules for Linux
49
50 * https://github.com/zfsonlinux/
51
52 For licensing questions, see: http://open-zfs.org/wiki/Talk:FAQ
53
54
55 FIRMWARE:
56 =========
57
58 We create our own firmware package, which includes the firmware for
59 all proxmox-ve kernels. So far this include
60
61 pve-kernel-2.6.18
62 pve-kernel-2.6.24
63 pve-kernel-2.6.32
64 pve-kernel-2.6.35
65
66 We use 'find-firmware.pl' to extract lists of required firmeware
67 files. The script 'assemble-firmware.pl' is used to read those lists
68 and copy the files from various source directory into a target
69 directory.
70
71 We do not include firmeware for some wireless HW when there is a
72 separate debian package for that, for example:
73
74 zd1211-firmware
75 atmel-firmware
76 bluez-firmware
77
78
79 PATCHES:
80 --------
81
82 bootsplash-3.1.9-2.6.31-rh.patch: bootsplash patch
83
84 bridge-patch.diff: Avoid bridge problems with changing MAC
85 see also: http://forum.openvz.org/index.php?t=msg&th=5291
86
87 Behaviour after 2.6.27 has changed slighly - after setting mac address
88 of bridge device, then address won't change. So we could omit
89 that patch, requiring to set hwaddress in /etc/network/interfaces.
90
91
92 Additional information
93 ----------------------
94
95 We use the default configuration provided by openvz, and apply
96 the following modification:
97
98 see config-2.6.32.diff
99
100 - enable bootsplash
101 CONFIG_FB_VESA=y
102 CONFIG_FRAMEBUFFER_CONSOLE=Y
103 CONFIG_BOOTSPLASH=y
104
105 - disable CONFIG_DEBUG_INFO
106
107 - disable CONFIG_PRINTK_TIME
108
109 - enable common CONFIG_BLK_DEV_XXX to avoid hardware detection
110 problems (udev, undate-initramfs hav serious problems without that)
111
112 CONFIG_BLK_DEV_SD=y
113 CONFIG_BLK_DEV_SR=y
114 CONFIG_BLK_DEV_DM=y
115
116 - disable module signatures (CONFIG_MODULE_SIG, CONFIG_CRYPTO_SIGNATURE)
117
118 - enable usbip (this is also enable on debian kernels)
119
120 CONFIG_USB_IP_COMMON=m
121 CONFIG_USB_IP_VHCI_HCD=m
122 CONFIG_USB_IP_HOST=m
123
124 - enable IBM JFS file system
125
126 This is disabled in RHEL kernel for no real reason, so we enable
127 it as requested by users (bug #64)
128
129 - enable apple HFS and HFSPLUS
130
131 This is disabled in RHEL kernel for no real reason, so we enable
132 it as requested by users
133
134 - enable CONFIG_BRIDGE=y
135
136 Else we get warnings on boot, that
137 net.bridge.bridge-nf-call-iptables is an unknown key
138
139 - disable CONFIG_BRIDGE_IGMP_SNOOPING
140
141 To avoid problems with multicasting. Various users reported
142 multipath problems, which can be avoided by turning off IGMP
143 snooping.
144
145 - use 'deadline' as default scheduler
146
147 This is the suggested setting for KVM. We also measure bad fsync
148 performance with ext4 and cfq.
149
150 - set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
151
152 because if not set, it can give some dynamic memory or cpu frequencies
153 change, and vms can crash (mainly windows guest).
154
155 see http://forum.proxmox.com/threads/18238-Windows-7-x64-VMs-crashing-randomly-during-process-termination?p=93273#post93273
156
157 Testing final kernel with kvm
158 -----------------------------
159
160 kvm -kernel data/boot/vmlinuz-2.6.32-6-pve -initrd initrd.img-2.6.32-6-pve -append "vga=791 video=vesafb:ywrap,mtrr splash=silent" /dev/zero
161