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