HW/VM Vendors Limitations

HW/VM Vendors Limitations

Before selecting a hardware or virtual-machine provider, review the common service limitations that may influence platform deployment, networking, storage, migration, and feature availability.

Different vendors expose different virtualization, networking, and storage capabilities. These restrictions can affect whether Virtuozzo Application Management can be deployed with its complete feature set or whether additional configuration is required.

On this page

Virtualization Technology

Virtualization technology describes the hypervisor or virtualization model used by a particular vendor. The selected technology can influence nested virtualization, storage behavior, networking, migration, and support for platform components.

Always verify that the provider’s virtualization layer is supported before finalizing the infrastructure design.

Platform Editions

Business Edition The standard Virtuozzo Application Management deployment with the complete platform feature set, business and technical support, and turnkey installation and configuration by platform engineers.
Lite Edition A lightweight personal PaaS intended for smaller customers with limited budgets. It is available through automated deployment on supported cloud providers using a preconfigured image.

The appropriate edition depends on the provider, deployment model, required feature set, expected scale, and support requirements.

Highly Available Storage

Highly available storage provides additional redundancy and reliability for platform workloads.

  • Cloud Storage cannot run on virtual machines and therefore requires bare-metal servers.
  • Virtuozzo Infrastructure includes its own highly available storage, so additional redundancy at the VM-host level is generally unnecessary.
Important: Cloud Storage deployment must be planned on physical servers because virtualization is not supported for this component.

Private Network Availability

Some service providers do not offer managed private Layer 2 networks or do not allow more than one internal IP address to be attached to a single VM.

In such cases, additional Open vSwitch overlay networks may be required to provide the internal network functionality expected by the platform.

IPv4/IPv6 External Network Availability

  • Some providers bind an IP address to a specific host. During container migration, the address would need to be reassigned to another host, which the platform does not currently support.
  • Some providers allow only one public IP address per VM, resulting in limited platform capabilities.
  • Some providers do not support direct public-IP attachment to node instances.
Public-IP behavior should be checked carefully when workload migration, dedicated IP addresses, or multiple public addresses per node are required.

Network Protocol Stack

Certain providers permit only a limited set of network protocols, commonly ICMP, UDP, TCP, and ESP. Verify protocol support when the intended application or platform integration depends on additional protocols.

Windows VM Support

Windows VM support is available only on bare-metal servers because nested virtualization is not supported.

A platform deployed primarily on virtual infrastructure can still support Windows VMs by adding a dedicated bare-metal host in a separate host group or region. That host must satisfy the hardware requirements for Windows virtualization.

Deployment option: Add a dedicated bare-metal host group or region specifically for Windows VM workloads when the primary platform infrastructure runs on virtual machines.

What’s next?