Article ID: 114925, created on Oct 9, 2012, last review on Apr 30, 2014

  • Applies to:
  • Virtuozzo hypervisor 5.0

Synopsis:          New Parallels Server Bare Metal 5.0 kernel provides
                   an update with security and stability fixes.
Product:           Parallels Server Bare Metal 5.0
Keywords:          "bugfix" "stability" "security"


This document provides information on the new Parallels Server Bare Metal 5.0
kernel, version 2.6.32-042stab062.2.


1. About This Release
2. Updates Description
3. Obtaining New Kernel
4. Required RPMs
5. References



The current update for the Parallels Server Bare Metal 5.0 kernel provides a
new kernel based on the Red Hat Enterprise Linux 6.3 kernel
(2.6.32-279.9.1.el6). The updated kernel includes a number of security and
stability fixes.



This update contains fixes for the following issues:

* The update introduces the kernel module option "tg3_pcie_mrrs_boost" that
  forces the PCI Maximum Read Request Size (MRRS) to increase to 4 KB.
  Normally, a Node's BIOS automatically configures the proper MRRS value for
  hardware. The "tg3_pcie_mrrs_boost" option is intended for use only on
  hardware with a broken BIOS.

  Boosting the MRRS value may increase the performance of network cards, but
  this may also cause some problems on specific hardware platforms. The related
  mainstream commit is 2c55a3d08ade44a778c182c220a7907ec65d5fb8. (PSBM-14240)

* It was impossible to stop a container with an external process in the "T"
  state. Such a situation could occur when a command executed via "vzctl exec"
  was suspended with Ctrl+z. (PCLIN-31083)

* Support for kernel compilation with gcc 4.7 was added. (OVZ 2339)

* VLANs inside containers could fail to work if the "e1000e" driver supported
  a Node's network card. (PCLIN-31132)

  Note: If a VLAN is configured on the Node, VLANs is containers may still
  fail to work. Therefore, if the "e1000e" network driver is used, either all VLANs
  you plan to use in containers must be created on the Hardware Node, or the
  Node must have no VLANs configured.

* Under certain circumstances, the Hardware Node could produce the following
  "unregister_netdevice: waiting for lo=... to become free. Usage count = 3" (PSBM-14858)

* Not cleaned up TCP hints in the TCP code might be reused by NFS connections
  after timeouts, causing a kernel panic. (PCLIN-31212)

* Using certain types of iptables rules in a container might cause a kernel
  panic if OpenVPN was configured in the container. (OVZ 2322)

* An issue with CPU soft lockups caused by calling inet_twsk_deschedule() with
  the bh enabled was fixed. (OVZ 2346)

* A bug in the ext4 code, which could cause a kernel panic, was fixed. (PCLIN-31215)

* A container online migration could fail if a process in the container
  opened a /proc/$PID/... file of a task and that task died. (OVZ 2315)

* Support for the online migration of mm->saved_auxv data was added. Migrating
  this data is needed, in particular, for process debugging with gdb after the
  online migration. (PSBM-13556)

* The NFS server v4 exclusive locks handling was fixed. (OVZ 2122)

* Memory leaks in the code that provides vznetstat statistics were fixed. (PSBM-15109)

* An issue with CPU hard lockups caused by deadlocks in gathering statistics
  code, which could lead to a kernel panic, has been fixed. (PCLIN-31259)



You can download and install this kernel update using the vzup2date utility
included in the Parallels Server Bare Metal 5.0 distribution set.



Depending on the processor installed on the Hardware Node, the following RPM
packages are included in the kernel update:




Copyright (c) 1999-2012 Parallels Holdings, Ltd. and its affiliates. All rights

c662da62f00df94fd77ba7a2c9eff4b4 2897d76d56d2010f4e3a28f864d69223 a26b38f94253cdfbf1028d72cf3a498b

Email subscription for changes to this article
Save as PDF