Article ID: 112334, created on Sep 20, 2011, last review on Jan 30, 2015

  • Applies to:
  • Virtuozzo containers for Linux

Information

This article describes how to upgrade Parallels Virtuozzo Containers for Linux 3.0 on CentOS 4.x to Parallels Containers 4.7 on CentOS 6.x.

NOTE: The total amount of time taken by the upgrade procedure and its particular steps may vary depending on the Internet connection speed and the number of packages installed.

NOTE: IT IS STRONGLY RECOMMENDED TO MAKE A FULL SERVER BACKUP IN CASE OF ACCIDENTALLY FORMATTING THE /vz PARTITION!

Upgrade sequence

  1. Upgrade Parallels Virtuozzo Containers 3.0 to 4.0 using the vzup2date command:
    vzup2date -s -m batch install --major --self-update

     
  2. After upgrading to Parallels Virtuozzo Containers 4.0, install all pending updates for this version:
    vzup2date -s -m batch install

     
  3. Back up the PVC-related data residing on the root partition:
    tar -cvzf /vz/vz_root_backup.tgz /etc/sysconfig/vz-scripts/*.conf /etc/sysconfig/vz /etc/vz/* /etc/cron.d/venetclean /etc/cron.d/vereboot

     
  4. Insert the CentOS 6 installation DVD into the DVD drive and reboot the server into the DVD installer.
     
  5. Follow the on-screen instructions to install CentOS 6 on the existing '/' partition.
    NOTE: Make sure that the /vz partition is not formatted during the installation.
     
  6. Once the installation finishes, reboot the server into CentOS 6.
     
  7. Download and install Parallels Virtuozzo Containers for Linux 4.7:
    112006 How to install a specific version of Parallels Containers for Linux.
     
  8. Once Parallels Containers for Linux 4.7 is installed, reboot the server into the PVCfL kernel.
     
  9. Extract the contents of /vz/vz_root_backup.tgz:
    tar -xvzf /vz/vz_root_backup.tgz -C /

     
  10. Restart the vz service.
    service vz restart

     
  11. Install the latest PVA 4.6 agent using the instructions from this article:
    9445 How to install/reinstall/upgrade to PVA 4.6 Agent on a PVC for Linux hardware node.

2897d76d56d2010f4e3a28f864d69223 e8e50b42231236b82df27684e7ec0beb d02f9caf3e11b191a38179103495106f

Email subscription for changes to this article
Save as PDF