FAQ

There are multiple billing models available for Virtuozzo Cloud:

• Hourly billing
• Monthly billing
• Monthly billing with prepayment

Monthly billing assumes a discount.

Currently, we have the following regions:

• eu1 - Frankfurt, Germany
• eu3 - Amsterdam, Netherlands
• uk1 - Manchester, UK
• us1 - Dallas, USA
• ap1 - Singapore (coming)

By default, no password is set to access a virtual machine. We do not recommend using passwords to access instances due to security reasons. Please use SSH Key as a secure way to access your instance.

Creating Virtual Machines

In addition, the password can be set using cloud-init script. Here is an example for Ubuntu and CentOS:

• for Ubuntu

1
2
3
4
5
6
7

#cloud-config
user: ubuntu
sudo: ALL=(ALL) ALL
groups: users, admin, wheel
password: (your password)
chpasswd: {expire: False}
ssh_pwauth: True

• for CentOS

1
2
3
4
5
6
7

#cloud-config
user: centos
sudo: ALL=(ALL) ALL
groups: users, admin, wheel
password: (your password)
chpasswd: {expire: False}
ssh_pwauth: True

In the wizard for creating a virtual machine, go to the “Customization script (optional)” section and paste a fragment of the configuration file, or upload the configuration file.

How to use the rescue mode - Rescuing Virtual Machines.

The philosophy behind rescue mode is that you connect to the failed virtual machine either using an ISO or a disk image of some boot environment from which you can interact with the disk image of the failed virtual machine. For example, you can use the GNOME Partition Editor bootable ISO to resize a disk partition that is full and prevents you from booting your VM’s operating system.

We provide site2site IPsec VPN to connect IaaS-based projects with 3d-party infrastructure based other private or public clouds. Here is the guide on how to configure site2site VPN - Managing VPN Connections.

We do not provide VPN service for end-users. However, customer can use a 3d-party solution. For example, a customer can upload an image of the popular pfSense solution to our cloud and create a virtual machine from it, which will act as a gateway and VPN endpoint. In this way, users can take advantage of the end-user VPN.

Virtuozzo Cloud provides a wide range of network management capabilities. Customers can create as many virtual networks as they need with complex topologies in the scope of the assigned project. To learn more about the networking capabilities of our cloud, we recommend reading the following documents:

• Managing Virtual Private Networks
• Preparing Network
• Managing VPN Connections
• Managing Virtual Routers
• Managing Floating IP Addresses
• Managing Load Balancers

This problem can occur because the virtual network must be created before the customer can create the virtual machine. The detailed process of creating a virtual machine is described in the document - Creating Virtual Machines.

Special attention should be paid to the “Prerequisites” section.

Currently, we provide the following images:

Please make sure that Docker MTU settings are equal to the MTU setting for your VM network. Otherwise, some applications running inside Docker containers might not work.

For example, you have a VM with the following network configuration:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: ens4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1413 qdisc fq_codel state UP group default qlen 1000
    link/ether fa:16:3e:fd:75:1a brd ff:ff:ff:ff:ff:ff
    altname enp0s4
    inet 10.0.0.64/24 metric 100 brd 10.0.0.255 scope global dynamic ens4
       valid_lft 24231sec preferred_lft 24231sec
    inet6 fe80::f816:3eff:fefd:751a/64 scope link
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:44:a4:40:fe brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:44ff:fea4:40fe/64 scope link
       valid_lft forever preferred_lft forever

Docker will have issues on this VM, as your ens4 and docker0 networks have different MTU configuration, as Docker sets MTU to 1500 bytes by default.

Do the following. Create a file with new MTU configuration:

1
2

$ vi /etc/docker/daemon.json
{"mtu": 1413}

Restart docker service:

1

$ systemctl restart docker.service

Enjoy.