Do I need static or portable IP addresses for Virtuozzo?

• Static IP address: Use a static IP address if you have only one hardware node (per VLAN or in total)
• Portable IP address:
  • Routed to VLAN: Use this method if you have multiple host nodes within the same VLAN. You also use this method to migrate a container to a different hardware node within the same VLAN without changing the IP of the container.
• Secondary on VLAN: This method works, but you don't need a secondary gateway. You lose 3 of the IP addresses due to host ID, gateway, and broadcast.

Costs per IP can change depending on the routing type (Routed to VLAN or Secondary on VLAN). Prices are shown in the portal after you select the server that you are ordering the IP addresses for. Routing can be changed at any time by opening a support ticket.

Can I migrate a Virtuozzo 3 Container to a Virtuozzo Container 4 hardware node with no downtime?

Linux:

Yes. By default, Virtuozzo Containers for Linux 4 run in compatibility mode. If Virtuozzo Containers is not running in compatibility mode, then you can start it by using the following command on the hardware node through SSH.

/usr/sbin/vzagent_compat_ctl start

Windows (unsupported):

With Virtuozzo Containers 4 Windows, you have downtime during the transition (between 20 seconds up to 5 minutes) because of not having an online option to pass.

If you use Virtuozzo 3.0 for Windows, then you need to upgrade the hardware node to at least Virtuozzo 3.5.1 for Windows.

Virtuozzo Containers 4 for Windows, by default, runs in compatibility mode.

Restoring backups from 3.5.1 on a Virtuozzo Containers 4 hardware node can also be performed by copying the full backup to the destination node, running vzbackupsync.exe and restoring the backup as normal.

Make sure that the same templates are installed on the new hardware node.

Are containers isolated from each other and the host?

Your containers are restricted from loading LKMs, performing a chroot(“../../../”) out of their own environment and don't share IPC Resources (semaphore sets and shared memory segments).

You have no security concerns with how Virtuozzo manages resources and isolates the processes. With a bridged network configuration, all containers in the same VLAN (on the same hardware node) can see each other's traffic. Using routed mode is highly suggested.

Why can't I cache RedHat and SUSE OS templates in Virtuozzo?

You can experience issues when you cache to RedHat and SUSE OS templates if you use Vitruozzo. These OS templates require extra licensing, which IBM Cloud doesn't provide. If you receive any of the following errors, you need to have your own accounts with the respective vendors and configure the corresponding variables within /etc/vztt/url.map (/etc/vztt/vztt.conf in Virtuozzo 3.)

Why can I ping my ServiceVE but can't log in to with SSH (PIM/PMC)?

Make sure that the host node doesn't have any IP addresses assigned other than the IP addresses that are listed in the Portal (1 public IP and 1 private IP [located in 10.0.0.0/8]).

If you have any range files that are configured on the host node, then you need to remove these files and restart networking.

[root@virtuozzo ~]# mv –vi /etc/sysconfig/network-scripts/eth[0-9]-range[0-9]* ~/.sl-orig-configs/

[root@virtuozzo ~]# /sbin/service network restart

vzcp isn't started within the Service VE. Start vzcp within the Service VE from the hardware node.

[root@virtuozzo ~]# vzctl exec2 1 service vzcp status

vzcp is stopped

[root@virtuozzo ~]# vzctl exec2 1 service vzcp start

Starting vzcpd: [  OK  ]

Starting vzcp: [  OK  ]

[root@virtuozzo ~]# vzctl exec2 1 service vzcp status

vzcp (pid 3775 3774 3771) is running...

[root@virtuozzo ~]#