OpenVZ Virtuozzo Containers Wiki - User contributions [en]

Compiling the OpenVZ kernel (the Debian way)

2008-11-07T07:16:07Z

MikhailGusarov:

== Lenny and above ==

Debian Lenny and Sid already include the openvz kernel (linux-image-${version}-openvz-${arch}), so the manual compilation is not necessary in many cases.

== Installing sources ==

To install the kernel-source and the OpenVZ kernel patch, run:
# apt-get install kernel-package linux-source-2.6.18 kernel-patch-openvz libncurses5-dev

For Debian version lenny and later you run the following instead:
# apt-get install kernel-package linux-source-2.6.18 linux-patch-openvz libncurses5-dev
or
# apt-get install kernel-package linux-source-2.6.24 linux-patch-openvz libncurses5-dev

== Unpacking ==

Unpack the kernel source:
<pre>
# cd /usr/src
# tar xjf linux-source-2.6.18.tar.bz2
# cd linux-source-2.6.18
</pre>

== Kernel config ==

You need a kernel config.
You can use the config of the debian-kernel:
# cp /boot/config-2.6.18-5-686 .config

'''Or''' get a 2.6.18 kernel configuration from
http://download.openvz.org/kernel/branches/2.6.18/current/configs/ (depending on your architecture; the below example is for i686):
# wget http://download.openvz.org/kernel/branches/2.6.18/current/configs/kernel-2.6.18-i686.config.ovz -O .config

== Patching and configuring ==

Now you can apply the openvz kernel patch and modify your kernel-config:
# ../kernel-patches/all/apply/openvz
# make menuconfig

You need the following OpenVZ kernel config settings:
(taken from OpenVZ Kernel 2.6.18-028test010.1 on 686)

<pre>
Filesystem
\_ [*] Second extended fs support (CONFIG_EXT2_FS)
\_ [*] Ext3 journalling file system support (CONFIG_EXT3_FS)
\_ [M] Quota Support (CONFIG_QUOTA)
\_ [*] Compatibility with older quotactl interface (CONFIG_QUOTA_COMPAT)
\_ [*]Quota format v2 support (CONFIG_QFMT_V2)
\_ [*] VPS filesystem (CONFIG_SIM_FS)
\_ [M] Virtuozzo Disk Quota support (CONFIG_VZ_QUOTA)
\-> [*] Per-user and per-group quota in Virtuozzo quota partitions (VZ_QUOTA_UGID)

Security
\->[ ] Enable different security models

OpenVZ ... (what else :-)
\_[*] Virtual Environment support (CONFIG_VE)
\_ <M> VE calls interface (CONFIG_VE_CALLS)
\_ <M> VE networking (CONFIG_VE_NETDEV)
\_ <M> Virtual ethernet device (CONFIG_VE_ETHDEV)
\_ <M> VE device (CONFIG_VZ_DEV)
\_ [*] VE netfiltering (CONFIG_VE_IPTABLES)
\_ <M> VE watchdog module (CONFIG_VZ_WDOG)
\_ <M> Checkpointing & restoring Virtual Environments (CONFIG_VZ_CHECKPOINT)

User resources ... (User Beancounters)
\_ [*] Enable user resource accounting (CONFIG_USER_RESOURCE)
\_ [*] Account physical memory usage ( CONFIG_USER_RSS_ACCOUNTING)
\_ [*] Account disk IO (CONFIG_UBC_IO_ACCT)
\_ [*] Account swap usage (CONFIG_USER_SWAP_ACCOUNTING)
\_ [*] Report resource usage in /proc (CONFIG_USER_RESOURCE_PROC)
\_ [*] User resources debug features (CONFIG_UBC_DEBUG)
\_ [*] Debug kmemsize with cache counters (CONFIG_UBC_DEBUG_KMEM)
</pre>

{{Note|better to build the kernel-headers as well, so afterward other kernel-modules can
be built without whole kernel tree (e.g. drbd -> drbd0.7-module-source)}}

See also : "make-kpkg --targets"

== Compiling ==

Compile your kernel (as user root, or you need the --rootcmd!)
# make-kpkg --append_to_version=-1-openvz --added_patches=openvz --revision=1 --initrd binary-arch
or all above with one step
# make-kpkg --append_to_version=-1-openvz --added_patches=openvz --revision=1 --initrd --config menuconfig binary-arch

== Installing ==
Install the kernel and update initramfs:

# dpkg -i ../linux-image-2.6.18-1-openvz_1_i386.deb
# update-initramfs -c -k 2.6.18-1-openvz

{{Note|update-initramfs is done, when make-kpkg is use with --initrd option}}
http://wiki.openvz.org/Installation_on_Debian_%28etch%29#Install_the_toolset
{{Note|update-grub can be configured by /etc/kernel-img.conf}}

== Bootloader ==

Update the bootloader (if not done before)

GRUB :

# /usr/sbin/update-grub

{{Note|since the Debian Etch release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub}}

LILO:

# lilo

== Installing the Tools and Configuring ==

Continue with [[Installation on Debian#Installing the user-level tools]]

[[Category: Debian]]
[[Category: Installation]]
[[Category: Kernel]]

Package managers

2007-11-13T21:30:49Z

MikhailGusarov:

With OpenVZ, you can run many different Linux distributions on a single box. One particular thing in which distributions differ is package management. This article summarizes how to perform various common package management tasks on a different distributions.

'''Feel free to add the missing pieces'''

{| class="wikitable"
! align="center" | Action
! RPM RHEL, Fedora, CentOS, Mandrake, ...
! DEB Debian, Ubuntu
! Ebuild Gentoo, Sabayon
|-
| colspan="4" align="center" | '''Basic queries'''
|-
! List of all installed packages
|| <code>rpm -qa</code>
|| <code>dpkg -l</code>
|| <code>equery list</code>
|-
! List of installing packages matching ''substr''
|| <code>rpm -qa ''\*substr\*''</code>
|| <code>dpkg -l ''\*substr\*''</code>
|| <code>equery list ''substr''</code>
|-
! Basic information about an installed ''package''
|| <code>rpm -qi ''package''</code>
|| <code>dpkg -p ''package''</code>
|| <code>-???-</code>
|-
! List of files in a given ''package''
|| <code>rpm -ql ''package''</code>
|| <code>dpkg -L ''package''</code>
|| <code>equery files ''package''</code>
|-
! Which package a ''file'' belongs to?
|| <code>rpm -qf ''file''</code>
|| <code>dpkg -S ''file''</code>
|| <code>equery belongs ''file''</code>
|-
| colspan="4" align="center" | '''Package installation/upgrade/removal'''
|-
! Install a package from local ''package_file''
|| <code>rpm -ihv ''package_file*.rpm''</code>
|| <code>dpkg -i ''package_file*.deb'' <ref name="apt">Usually it is not necessary to download packages manually and install them. Use apt-cache search ''name'' to search for package in configured repositories and apt-get install ''package'' to install package and all it's dependencies</ref></code>
|| <code>-???-</code>
|-
! Upgrade a package from local ''package_file''
|| <code>rpm -Uhv ''package_file*.rpm''</code>
|| <code>dpkg -i ''package_file*.deb'' <ref name="apt"/></code>
|| <code>-???-</code>
|-
! Remove an installed ''package''
|| <code>rpm -e ''package''</code>
|| <code>dpkg -r ''package''</code>
|| <code>emerge --unmerge ''package''</code> 
<code>emerge --prune ''package''</code>
|-|}

<references/>

Kernel configuration

2007-02-21T16:37:54Z

MikhailGusarov: 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...

== 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]]

Talk:Installation on Debian/old

2007-02-09T13:19:42Z

MikhailGusarov:

info about needed modules in kernel-config

info about "Yet Another mkInitRD" yaid tools creating initrd-files

== ip_forward setup ==

If you want network access for the virtual server then you need to enable IP forwarding.
Set "ip_forward" to yes in /etc/network option.
# editor /etc/network/options

: /etc/network/options is deprecated. ip_forward may be enabled in /etc/sysctl.conf by adding the line "net.ipv4.ip_forward=1"

Talk:Installation on Debian/old

2007-02-09T13:19:01Z

MikhailGusarov: ip_forward setup

info about needed modules in kernel-config

info about "Yet Another mkInitRD" yaid tools creating initrd-files

== ip_forward setup ==

If you want network access for the virtual server then you need to enable IP forwarding. Set "ip_forward" to yes in /etc/network/option.
# editor /etc/network/options

: /etc/network/options is deprecated. ip_forward may be enabled in /etc/sysctl.conf by adding the line "net.ipv4.ip_forward=1"