• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 112060, created on Aug 25, 2011, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo containers for Windows


This article describes the best practices and known limitations of Virtuozzo containers for Windows technology from an end user's point of view.

The article will help you better understand OS virtualization technology capabilities and choose an appropriate usage scenario for your Virtuozzo containers product.

NOTE: You can put the information from this article into every Windows Container in your environment using the BgInfo tool:

113213 How to propagate Virtuozzo containers for Windows best practices to end customers

Known limitations

Despite the higher densities and faster management operations provided by container virtualization over hypervisor solutions, the fact that containers share the same OS kernel with the host leads to certain restrictions on their use. This section provides recommendations to follow when deploying and maintaining Virtuozzo containers for Windows. These recommendations are imposed by the nature of OS virtualization.

  1. Microsoft Updates and Internet Explorer versions

    Virtuozzo containers for Windows automatically applies all Microsoft Windows updates that are installed on the physical server to containers. Always use the Windows Automatic Update service on the server to update Windows software. Do not try to perform updates manually or via Microsoft's website. The version of Internet Explorer (IE) must be the same on the physical server as inside all containers hosted on this server.

    NOTE: Customers must not install Windows and IE updates manually. Present the automatic update of containers to customers as one of the main advantages of containers technology.

    Related Knowledgebase articles:

    • 113634: Microsoft Updates and Virtuozzo containers for Windows
    • 113428: How to know if an unsupported Microsoft update can be installed on a VC node
    • 123116: Which Internet Explorer versions are supported on Virtuozzo containers for Windows?
    • 5605: [Info] Is it possible to create a template of Internet Explorer 7?
    • 7084: How to create an Internet Explorer 8 MUI pack template
  2. Antiviruses

    We recommend installing the required antivirus (AV) solutions on the physical server. Since all containers share the same OS kernel with the host, no antivirus software should be installed inside containers. Antivirus software installed on the physical server detects all viruses inside containers. This provides great savings, as customers only need to install one copy of an AV solution to protect both the physical server and all containers running on it.

    NOTE: Customers must not install any antivirus software inside containers. The service provider should install one copy of the antivirus software on the hardware OS itself.

    Related Knowledgebase article:

    • 9589: Antivirus software compatibility with Virtuozzo containers 4.6
  3. Third-party drivers inside containers

    The Virtuozzo containers for Windows virtualization core intentionally blocks all untested third-party drivers inside containers for the sake of host security and Hardware Node stability.

    If you want to run an application with custom drivers inside containers, we suggest creating a feature request to Virtuozzo Development via an Virtuozzo Support Ticket to implement and verify the support of the driver.

    Related Knowledgebase article:

    • 8533: A driver installed inside containers is blocked from loading
  4. Complex network software inside containers

    The current version of Virtuozzo containers for Windows only supports using the Microsoft Windows VPN inside containers.

    NOTE: CCProxy, OpenVPN, Cisco AnyConnect, Hamachi, and any other non-Micosoft VPN software is not supported inside containers.

    Related Knowledgebase articles:

    • 1601: [Info] Is a VPN client supported inside a VE?
    • 6429: How to start Secure Socket Tunneling Protocol (SSTP) inside a container
  5. VSS backups inside containers

    If a backup solution that uses VSS for creating disk snapshots is installed inside a Virtuozzo container, it cannot create snapshots of the container system drive (C:), only snapshots of its additional drives. We recommend using native Virtuozzo backup tools on the physical server.

    Related Knowledgebase articles:

    • 1968: [Info] Does Virtuozzo 4.0 support any third-party backup solutions?
    • 8527: [Info] Do Virtuozzo 4.5 and 4.6 support any third party backup solutions?
    • 6289: How can I back up and restore data inside containers by means of third-party backup solutions?
    • 111678: Unable to create system state backup of Virtuozzo containers server using IBM Tivoli Storage Manager
  6. Application templates:

    There are several limitations for application templates due to the OS-level virtualization design.

    Related Knowledgebase article:

    • 112675: Application template limitations in Virtuozzo containers for Windows
  7. Microsoft Service packs

    If Virtuozzo containers for Windows was installed on Windows Server with some Service Pack (or none), all containers based on this server will run on using the same Service Pack (or none). In this case, neither container provisioning with another service pack nor the according template installation will be possible.

Best practices

  1. General use-cases

    Virtuozzo containers for Windows is highly recommended for hosters deploying small- and medium-sized containers that do not run mission-critical applications. The recommended scenarios are:

    • Platform for IIS hosting
    • Platform for Plesk hosting
    • Remote desktop and VDI (Firefox, MS Office, Skype, Acrobat Reader)
  2. High-availability offerings

    Using the Microsoft Windows clustering software, you can create a Virtuozzo failover cluster consisting of two or more Hardware Nodes and providing failover support for Virtuozzo mission-critical services and containers. If one Hardware Node in the cluster fails or is taken offline as part of planned maintenance, the services and containers from the problem server are automatically failed over to another Node in the cluster.

    NOTE: Virtuozzo containers for Windows technology itself does not provide an SLA greater than 99.5%.

  3. Virtuozzo containers for Windows versions

    To use the full power of high-performance servers, Virtuozzo recommends using the 64-bit version of Virtuozzo containers 4.6. The 64-bit version can be installed on servers running Windows Server 2008 R2 or the x86-64 editions of Windows Server 2008 and Windows Server 2003.

    NOTE: We do not recommend using 32-bit versions of Windows for resource-consuming containers with web and database hosting. Due to the non-paged pool limitation of 32-bit versions of Windows, the density of containers with web and database hosting servers decreases significantly.

    Related Knowledgebase articles:

    • 1675: [How To] Troubleshooting paged and nonpaged memory pool shortage (Event ID 2019 or 2020)
  4. Virtuozzo containers for Windows container parameters

    NOTE: These parameters are approximate and apply to a typical container configuration. Some applications may require higher RAM and numproc limits. Consider application-specific requirements when setting up resource limits for containers.

  5. Memory-hungry applications inside containers

    A container does not have its own paging file and its memory limit defines a portion of the paging file on the server assigned to this container. If customers run a memory-intensive application inside a container, the memory limit for this container must be set high enough to provide optimal application performance. Therefore, the service provider must provide appropriate guidance to the end-customer regarding the intended use and the appropriate level of memory availability for that customer’s VPS.

  6. Backups

    Virtuozzo containers for Windows has a native backup tool that allows users to easily backup and restore the entire contents of containers. There is no need to install backup applications inside containers unless the application requires application-level backups (e.g., to restore individual Microsoft Exchange mailboxes). Customers can also use any of the supported third-party backup tools to back up and restore containers.

    NOTE: We highly recommend backing up containers regularly.

    NOTE: Customers do not need to install backup applications inside containers unless they want to create application-level backups. In this case, they need to install a VSS-aware application on an additional drive rather than on the system drive (C). See the Usage Limitations section for more details.

    NOTE: For the best experience with Virtuozzo containers for Windows, we recommend backing up large containers to local storage and then transferring the resulting backups to network storage if required.

    NOTE: In addition to incremental and differential backups, we highly recommend creating full backups at regular intervals.

  7. Migration

    Before migrating containers, always make sure that both physical servers have the same set of Microsoft updates and the same version of Internet Explorer installed.

    Related Knowledgebase article:

    • 3591: [Info] OS version compatibility for containers migration
    • 126432 [HUB] Windows containers migration
  8. Databases

    We highly recommend using Microsoft SQL or MySQL databases inside containers.

    NOTE: If a customer plans to use other databases inside a container, please ensure that the memory limit for the container is set high enough to provide the optimal database performance.

  9. Microsoft .NET Framework

    Virtuozzo containers for Windows itself does not require the .NET Framework to function, which is why it is not necessary to install .NET Framework packages on the Hardware Node to make it work inside containers. If an application inside a container requires the .NET Framework, it will need to be installed directly inside the container.

    NOTE: .NET Framework versions differ among OS versions. Consider the OS compatibility table when installing the .NET Framework:

    111448: How do I properly install .NET Framework inside containers?

  10. Defragmentation

    To achieve the best performance and reduce disk space usage, it is strongly recommended that you perform disk defragmentation for both the Hardware Node and the containers on a regular basis.

    Related Knowledgebase article:

    • 114828: Disk defragmentation in containers best practices

Search Words

parallels virtuozzo containers for windows

enabling shadow copy

windows updates


actualizar internet explorer virtuozzo windows

error occurred while an initial user program was starting



VzkrnlStartVps failed dwErr=0x000004FB

ユーザ追加 IE エラー

best practices


known issues

virtuozzo API function call 'vzkrnlStartVps' failed dwErr=0x000004FB

PDB signature not found in database


service pack

How we can move the old data from the old container to the new container

2897d76d56d2010f4e3a28f864d69223 965b49118115a610e93635d21c5694a8 d02f9caf3e11b191a38179103495106f

Email subscription for changes to this article
Save as PDF