Kernel configuration - Revision history

Elronxenu: more grammar

2007-07-10T07:41:23Z

more grammar

Elronxenu: spelling, grammar

2007-07-10T07:37:04Z

spelling, grammar

Kir: /* OpenVZ related kernel config options */

2007-06-13T09:32:31Z

‎OpenVZ related kernel config options

Master: /* OpenVZ related kernel config options */

2007-06-12T22:22:56Z

‎OpenVZ related kernel config options

Dev at 15:25, 23 March 2007

2007-03-23T15:25:59Z

Kir: added intro, mention cpulimits/cpuunits

2007-02-22T05:40:06Z

added intro, mention cpulimits/cpuunits

MikhailGusarov: New page: == ACPI sleep == It is a bit tricky to make ACPI sleep and OpenVZ work together. ACPI sleep is enabled by `ACPI_SLEEP` kernel option. The following dependencies are declared i...

2007-02-21T16:37:54Z

New page: == ACPI sleep == It is a bit tricky to make ACPI sleep and OpenVZ work together. ACPI sleep is enabled by <code>ACPI_SLEEP</code> kernel option. The following dependencies are declared i...

New page

== ACPI sleep ==

It is a bit tricky to make ACPI sleep and OpenVZ work together.

ACPI sleep is enabled by <code>ACPI_SLEEP</code> kernel option. The following dependencies are declared in kernel configs:

ACPI_SLEEP depends on X86 && (!SMP || SUSPEND_SMP)
SUSPEND_SMP depends on HOTPLUG_CPU && X86 && PM
FAIRSCHED depends on SCHED_VCPU

And <code>SCHED_VCPU</code> is incompatible with <code>HOTPLUG_CPU</code>:

./kernel/cpu.c:#error "CONFIG_HOTPLUG_CPU isn't supported with CONFIG_SCHED_VCPU"

On non-SMP machine, you may disable <code>SMP</code>, this will resolve the conflict.

If you have SMP machine, you can only disable <code>FAIRSCHED</code> and <code>SCHED_VCPU</code>. This will loose isolation between VEs (scheduling will be performed per-task, not per-VE), but it is acceptable solution if your VEs are trusted (and it's hard to imagine untrusted VEs on notebook ;)

[[Category:Kernel]]

@@ Line 40: / Line 40: @@
   ./kernel/cpu.c:#error "CONFIG_HOTPLUG_CPU isn't supported with CONFIG_SCHED_VCPU"
-On non-SMP machine, you may disable <code>SMP</code>, this will resolve the conflict.
+On a non-SMP machine, you may disable <code>SMP</code>, this will resolve the conflict.
-If you have SMP machine, you can only disable <code>FAIRSCHED</code> and <code>SCHED_VCPU</code>. It will reduce some isolation between VEs (CPU scheduling will be performed per-task, not per-VE, and <code>cpuunits</code> and <code>cpulimit</code> settings will not take effect), but it is an acceptable solution if your VEs are trusted (and it's hard to imagine untrusted VEs on a notebook.)
+If you have an SMP machine, you can only disable <code>FAIRSCHED</code> and <code>SCHED_VCPU</code>. It will reduce some isolation between VEs (CPU scheduling will be performed per-task, not per-VE, and <code>cpuunits</code> and <code>cpulimit</code> settings will not take effect), but it is an acceptable solution if your VEs are trusted (and it's hard to imagine untrusted VEs on a notebook.)
 [[Category:Kernel]]
 [[Category:HOWTO]]

@@ Line 42: / Line 42: @@
 On non-SMP machine, you may disable <code>SMP</code>, this will resolve the conflict.
-If you have SMP machine, you can only disable <code>FAIRSCHED</code> and <code>SCHED_VCPU</code>. This will loose some isolation between VEs (CPU scheduling will be performed per-task, not per-VE, and <code>cpuunits</code> and <code>cpulimit</code> settings will not take effect), but it is acceptable solution if your VEs are trusted (and it's hard to imagine untrusted VEs on a notebook ;)
+If you have SMP machine, you can only disable <code>FAIRSCHED</code> and <code>SCHED_VCPU</code>. It will reduce some isolation between VEs (CPU scheduling will be performed per-task, not per-VE, and <code>cpuunits</code> and <code>cpulimit</code> settings will not take effect), but it is an acceptable solution if your VEs are trusted (and it's hard to imagine untrusted VEs on a notebook.)
 [[Category:Kernel]]
 [[Category:HOWTO]]

@@ Line 21: / Line 21: @@
   CONFIG_VE_IPTABLES=y
   CONFIG_VZ_WDOG=m
-  CONFIG_VZ_CHECKPOINT=m  #(CONFIG_VZ_CHECKPOINT=n on sparc)
 == ACPI sleep ==

@@ Line 21: / Line 21: @@
   CONFIG_VE_IPTABLES=y
   CONFIG_VZ_WDOG=m
-  CONFIG_VZ_CHECKPOINT=m
+  CONFIG_VZ_CHECKPOINT=m  #(CONFIG_VZ_CHECKPOINT=n on sparc)
 == ACPI sleep ==

← Older revision		Revision as of 15:25, 23 March 2007
Line 1:		Line 1:
	This article summarises various kernel configuration issues.		This article summarises various kernel configuration issues.
		+
		+	== OpenVZ related kernel config options ==
		+
		+	Please make sure the following config options are enabled
		+	in your kernel .config file before compilation process:
		+	CONFIG_SCHED_VCPU=y
		+	CONFIG_FAIRSCHED=y
		+
		+	CONFIG_SIM_FS=m
		+	CONFIG_VZ_QUOTA=m
		+	# CONFIG_VZ_QUOTA_UNLOAD is not set
		+	CONFIG_VZ_QUOTA_UGID=y
		+
		+	CONFIG_VE=y
		+	CONFIG_VE_CALLS=m
		+	CONFIG_VZ_GENCALLS=y
		+	CONFIG_VE_NETDEV=m
		+	CONFIG_VE_ETHDEV=m
		+	CONFIG_VZ_DEV=m
		+	CONFIG_VE_IPTABLES=y
		+	CONFIG_VZ_WDOG=m
		+	CONFIG_VZ_CHECKPOINT=m

	== ACPI sleep ==		== ACPI sleep ==