[pve-kernel-3.10.0.git] / README

KERNEL SOURCE:
==============

We use the CENTOS7/RHEL7 kernel sources, available from:

http://vault.centos.org/

or

http://oss.oracle.com/ol7/SRPMS-updates/


Additional/Updated Modules:
---------------------------

- include latest ixgbe driver from intel/sourceforge

- include latest igb driver from intel/sourceforge

- include latest e1000e driver from intel/sourceforge

#- include latest Broadcom bnx2 drivers: http://driverdownloads.qlogic.com/
#
#  * original file linux-7.11.05.zip contains
#    netxtreme2-7.11.05.tar.gz (added to repository)
#
#- include latest Adaptec aacraid driver
#
#  * http://download.adaptec.com/raid/aac/linux/aacraid-linux-src-1.2.1-40300.tgz

- include latest ARECA RAID drivers

  * http://www.areca.com.tw/support/s_linux/linux.htm

- include native OpenZFS filesystem kernel modules for Linux

  * https://github.com/zfsonlinux/

  For licensing questions, see: http://open-zfs.org/wiki/Talk:FAQ

- include latest HPSA driver (HP Smart Array)

  * http://sourceforge.net/projects/cciss/


FIRMWARE:
=========

We create our own firmware package, which includes the firmware for
all proxmox-ve kernels. So far this include

pve-kernel-2.6.18
pve-kernel-2.6.24
pve-kernel-2.6.32
pve-kernel-2.6.35
pve-kernel-3.10.0

We use 'find-firmware.pl' to extract lists of required firmeware
files.  The script 'assemble-firmware.pl' is used to read those lists
and copy the files from various source directory into a target
directory.

We do not include firmeware for some wireless HW when there is a
separate debian package for that, for example:

zd1211-firmware
atmel-firmware
bluez-firmware 


PATCHES:
--------

 bridge-patch.diff: Avoid bridge problems with changing MAC
  see also: http://forum.openvz.org/index.php?t=msg&th=5291

  Behaviour after 2.6.27 has changed slighly - after setting mac address
  of bridge device, then address won't change. So we could omit
  that patch, requiring to set hwaddress in /etc/network/interfaces.


Additional information
----------------------

We use the default configuration provided by RHEL, and apply
the following modification:

see config-3.10.0.diff

- enable CONFIG_CEPH_FS=m (request from user)

- enable common CONFIG_BLK_DEV_XXX to avoid hardware detection
  problems (udev, undate-initramfs hav serious problems without that)

  	 CONFIG_BLK_DEV_SD=y
  	 CONFIG_BLK_DEV_SR=y
  	 CONFIG_BLK_DEV_DM=y

- compile NBD and RBD modules
	 CONFIG_BLK_DEV_NBD=m
	 CONFIG_BLK_DEV_RBD=m

- set LOOP_MIN_COUNT to 8 (debian defaults)
	 CONFIG_BLK_DEV_LOOP_MIN_COUNT=8

- disable module signatures (CONFIG_MODULE_SIG)
 
- enable IBM JFS file system 

  This is disabled in RHEL kernel for no real reason, so we enable
  it as requested by users (bug #64)

- enable apple HFS and HFSPLUS

  This is disabled in RHEL kernel for no real reason, so we enable
  it as requested by users

- enable CONFIG_BCACHE=m (requested by user)

- enable CONFIG_BRIDGE=y

  Else we get warnings on boot, that
  net.bridge.bridge-nf-call-iptables is an unknown key

- disable CONFIG_DEFAULT_SECURITY_SELINUX

  Use same SELINUX config as debian kernels (CONFIG_DEFAULT_SECURITY_DAC=y)

- set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y

  because if not set, it can give some dynamic memory or cpu frequencies 
  change, and vms can crash (mainly windows guest).

  see http://forum.proxmox.com/threads/18238-Windows-7-x64-VMs-crashing-randomly-during-process-termination?p=93273#post93273

- set CONFIG_CC_STACKPROTECTOR_REGULAR=y

  gcc on debian wheezy does not supportCONFIG_CC_STACKPROTECTOR_STRONG
 
# Note: enable now for testing
#- disable CONFIG_BRIDGE_IGMP_SNOOPING 
#
# To avoid problems with multicasting. Various users reported
#  multipath problems, which can be avoided by turning off IGMP
# snooping.

# deadline is default anyways now
#- use 'deadline' as default scheduler
#
#  This is the suggested setting for KVM. We also measure bad fsync
#  performance with ext4 and cfq.

Testing final kernel with kvm
-----------------------------

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
Commit	Line	Data
688f31fc DM	1	KERNEL SOURCE:
	2	==============
	3
9514acf0	4	We use the CENTOS7/RHEL7 kernel sources, available from:
688f31fc	5
9514acf0	6	http://vault.centos.org/
688f31fc	7
5b7b98d4 DM	8	or
	9
	10	http://oss.oracle.com/ol7/SRPMS-updates/
	11
688f31fc DM	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
a4bc2c8c DM	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
688f31fc DM	30
	31	- include latest ARECA RAID drivers
	32
	33	* http://www.areca.com.tw/support/s_linux/linux.htm
	34
6f46143a DM	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
b3552c48 DM	41	- include latest HPSA driver (HP Smart Array)
	42
	43	* http://sourceforge.net/projects/cciss/
	44
6f46143a	45
688f31fc DM	46	FIRMWARE:
	47	=========
	48
	49	We create our own firmware package, which includes the firmware for
	50	all proxmox-ve kernels. So far this include
	51
	52	pve-kernel-2.6.18
	53	pve-kernel-2.6.24
	54	pve-kernel-2.6.32
	55	pve-kernel-2.6.35
	56	pve-kernel-3.10.0
	57
	58	We use 'find-firmware.pl' to extract lists of required firmeware
	59	files. The script 'assemble-firmware.pl' is used to read those lists
	60	and copy the files from various source directory into a target
	61	directory.
	62
	63	We do not include firmeware for some wireless HW when there is a
	64	separate debian package for that, for example:
	65
	66	zd1211-firmware
	67	atmel-firmware
	68	bluez-firmware
	69
	70
	71	PATCHES:
	72	--------
	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
	81
	82	Additional information
	83	----------------------
	84
	85	We use the default configuration provided by RHEL, and apply
	86	the following modification:
	87
	88	see config-3.10.0.diff
	89
79f048f2 DM	90	- enable CONFIG_CEPH_FS=m (request from user)
79f048f2 DM	91
688f31fc DM	92	- enable common CONFIG_BLK_DEV_XXX to avoid hardware detection
	93	problems (udev, undate-initramfs hav serious problems without that)
	94
	95	CONFIG_BLK_DEV_SD=y
	96	CONFIG_BLK_DEV_SR=y
	97	CONFIG_BLK_DEV_DM=y
	98
2600940a DM	99	- compile NBD and RBD modules
	100	CONFIG_BLK_DEV_NBD=m
	101	CONFIG_BLK_DEV_RBD=m
	102
	103	- set LOOP_MIN_COUNT to 8 (debian defaults)
	104	CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
	105
688f31fc DM	106	- disable module signatures (CONFIG_MODULE_SIG)
	107
	108	- enable IBM JFS file system
	109
	110	This is disabled in RHEL kernel for no real reason, so we enable
	111	it as requested by users (bug #64)
	112
	113	- enable apple HFS and HFSPLUS
	114
	115	This is disabled in RHEL kernel for no real reason, so we enable
	116	it as requested by users
	117
bfcb7405 DM	118	- enable CONFIG_BCACHE=m (requested by user)
bfcb7405 DM	119
688f31fc DM	120	- enable CONFIG_BRIDGE=y
	121
	122	Else we get warnings on boot, that
	123	net.bridge.bridge-nf-call-iptables is an unknown key
	124
f396caf4 DM	125	- disable CONFIG_DEFAULT_SECURITY_SELINUX
	126
	127	Use same SELINUX config as debian kernels (CONFIG_DEFAULT_SECURITY_DAC=y)
	128
db697728 DM	129	- set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
	130
	131	because if not set, it can give some dynamic memory or cpu frequencies
	132	change, and vms can crash (mainly windows guest).
	133
	134	see http://forum.proxmox.com/threads/18238-Windows-7-x64-VMs-crashing-randomly-during-process-termination?p=93273#post93273
	135
062da07d DM	136	- set CONFIG_CC_STACKPROTECTOR_REGULAR=y
	137
	138	gcc on debian wheezy does not supportCONFIG_CC_STACKPROTECTOR_STRONG
	139
688f31fc DM	140	# Note: enable now for testing
	141	#- disable CONFIG_BRIDGE_IGMP_SNOOPING
	142	#
	143	# To avoid problems with multicasting. Various users reported
	144	# multipath problems, which can be avoided by turning off IGMP
	145	# snooping.
	146
	147	# deadline is default anyways now
	148	#- use 'deadline' as default scheduler
	149	#
	150	# This is the suggested setting for KVM. We also measure bad fsync
	151	# performance with ext4 and cfq.
	152
	153	Testing final kernel with kvm
	154	-----------------------------
	155
062da07d	156	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
688f31fc	157