Proxmox VE Kernel: Difference between revisions

From Proxmox VE
Jump to navigation Jump to search
Line 34: Line 34:
* This kernel has no OpenVZ support
* This kernel has no OpenVZ support
==How to install 2.6.32==
==How to install 2.6.32==
Please disable OpenVZ startup first. Just edit file /etc/vz/vz.conf and set
<pre>VIRTUOZZO=no</pre>
Then run the following commands
<pre>apt-get update
<pre>apt-get update
apt-get upgrade
apt-get upgrade

Revision as of 12:54, 12 January 2010

(Currently available via the pvetest repository, see forum post)

Introduction

Proxmox publishes three kernel branches, each one with minor feature differences. Currently, the 2.6.24 is the default and recommended branch - included from Proxmox VE 0.9 beta till Proxmox 1.4 (the current stable).

A Proxmox VE cluster master can manage a mixed kernel setup. For example, you can run two nodes with 2.6.18 and two nodes with 2.6.32 and also nodes with 2.6.24. Depending on the features, some migrations are only possible between identical kernels.

All three kernel branches are using DRBD 8.3.4.

Kernel 2.6.18

  • Stable OpenVZ
  • KVM

How to install 2.6.18

apt-get update
apt-get upgrade
apt-get install proxmox-ve-2.6.18

To make sure that you boot into the new kernel, check /boot/grub/menu.lst. Now reboot and check if the system is running the right kernel.

Kernel 2.6.24

  • OpenVZ
  • KVM

How to install 2.6.24

apt-get update
apt-get upgrade
apt-get install proxmox-ve-2.6.24

To make sure that you boot into the new kernel, check /boot/grub/menu.lst. Now reboot and check if the system is running the right kernel.

Kernel 2.6.32

  • Latest KVM with KSM (shares identical memory pages, especially useful when running multiple guests from the same or similar base operating system image. Because memory is shared, the combined memory usage of the guests is reduced)
  • This kernel has no OpenVZ support

How to install 2.6.32

apt-get update
apt-get upgrade
apt-get install proxmox-ve-2.6.32

To make sure that you boot into the new kernel, check /boot/grub/menu.lst. Now reboot and check if the system is running the right kernel.