Virtual Machines FAQ
Virtual server configurations are subject to the following limits, according to the CPU type:
- AMD CPU: Up to 62 cores and 230 GB RAM
- Intel® CPU: Up to 51 Intel® cores and 230 GB RAM
A single Intel® physical core with Hyper-Threading Technology is exposed to the operating system of your virtual server as two distinct “logical cores”, which process separate threads.
Because the size of the working memory (RAM) cannot be processed during the initial configuration, newly provisioned servers with more than 8 GB of RAM may not start successfully when created from IONOS Windows images.
We recommend initially setting the RAM size to 8 GB; RAM size can then be scaled as needed after the initial provisioning and configuration.
- Minimum: 1 GB
- Maximum: 4 TB
- Minimum: 1 GB
- Maximum: 4 TB
You can scale up the HDD and SSD storage volumes on need basis.
IONOS data centers are divided into separate areas called Availability Zones.
You can enhance reliability and set up high-availability scenarios by deploying redundant virtual servers and storage devices across multiple Availability Zones.
- Select the server in the DCD Workspace
- Use Inspector > Properties > Availability Zone menu to change the Availability Zone
Live Vertical Scaling (LVS) technology permits you to scale the number of CPU cores and amount of RAM while the server is running, without having to restart it. Please note that Windows only allows scaling the number of CPU cores, but not the amount of RAM. For scaling to more than eight CPU cores, Windows requires a reboot.
Servers can be restarted at the operating system level (using the reboot command, for instance). You can also use the DCD reset function, which functions similarly to a physical server's reset button.
You should use DCD to shut down your server completely. Your VM will then be marked as "shut down" in the DCD. Shutting down a VM at the operating system level alone does not deallocate its resources or suspend the billing.
You can delete a server in the DCD Workspace by right-clicking it and selecting Delete, or by selecting (clicking) the server and pressing the
Try to connect to your VM using the Remote Console to see if it is up and running. If you have trouble logging on to your VM, please provide our support team with screenshots of error messages and prompts from the Remote Console.
- Windows users: Please send us a screenshot of the Task Manager.
- Linux users: Please send us the output of
When using IONOS-provided images, you set the passwords yourself prior to provisioning.
Newly provisioned servers with more than 8 GB of RAM may not start successfully when created from IONOS Windows images, because the RAM size cannot be processed during the initial configuration.
An error is displayed according to the server version; for example, Windows Server 2012 R2 displays the following message:
"Windows could not finish configuring the system. To attempt to resume configuration, restart the computer."
We recommend initially setting the RAM size to 8 GB, and rescaling it as needed after the initial provisioning and configuration is complete.
The choice of CPU architecture primarily depends on your workload and performance requirements. Intel® processors are oftentimes more powerful than AMD processors. Intel® processors are designed for compute-intensive applications and workloads where the benefits of hyperthreading and multitasking can be fully exploited. Intel® cores cost twice as much as AMD cores. Therefore, it is recommended that you measure and compare the actual performance of both CPU architectures against your own workload. You can change the CPU type in the DCD or use the API, and see for yourself whether Intel® processors deliver significant performance gains, or more economical AMD cores still meet your requirements.
With our unique "Core Technology Choice" feature, we are the only cloud computing provider that makes it possible to flexibly change the processor architecture per virtual instance.
When the cursor disappears after logging on to the Remote Console, you can reconnect to the server using the appropriate menu entry.
For a long time, the duopoly of virtual private servers (VPS) and dedicated cloud servers dominated virtualized computing environments.
Enter Cloud Cubes — virtual private service instances — the next generation of IaaS. Developed by IONOS Cloud, Cubes are ideal for specific workloads that do not require high compute performance from all resources at all times — development and testing environments, website hosting, simple web applications, and so on.
While based on shared resources, the Cubes can rival physical servers through a platform design that can redistribute available performance capacities among individual instances. At the same time, reduced operational complexity and highly optimized resource utilization translate into lower operating costs.
Cubes instances come complete with vCPUs, RAM, and direct-attached NVMe storage volumes; choose among standard configurations by selecting one of several templates for your Cubes. Storage capacities can be expanded further by adding network block storage units to your Cubes.
Cubes instances can be used together with all enterprise-grade features, resources, and services, offered by IONOS Cloud.
Affordable, quickly available, and with everything you need — have your Cubes up and running in minutes in the IONOS Cloud.
The device monitors VM/OS crashes. PVPanic is a simulated device, through which a guest panic event is sent to the hypervisor, and a QMP event is generated.
No, the PVPanic device is plug-and-play. However, installing drivers may require a restart.
This is no cause for concern. First of all, you do not need to reboot the VM. However, you will need to reinstall appropriate drivers (which are provided by IONOS Cloud).
There are no issues found when enabling pvpanic. However, users can’t choose whether or not to enable the device - it is always available for use.
Something else to consider - PVPanic does not offer bidirectional communication between the VM and the hypervisor. Instead, the communication only goes from the VM towards the hypervisor.
There are no special requirements or limitations to any components of a virtualized server. Therefore, PVPanic is completely compatible with AMD and Intel processors.
The PVPanic device is implemented as an ISA device (using IOPORT).
Check the kernel config
m = PVPanic device is available as module y = PVPanic device is native available in the kernel n = PVPanic device is not available
When the device is not available (
CONFIG_PVPANIC=n), use another kernel or image.
For your virtual machines running Microsoft Windows, we provide an ISO image that includes all the relevant drivers for your instance. Just log into DCD, open your chosen virtual data center, add a CD-ROM drive and insert the driver ISO as shown below (this can also be done via CloudAPI).
Create a new CD-ROM
Please note that a reboot is required to add the CD drive.
Once provisioning is complete, you can log into your OS by adding drivers for the unknown device through the Device Manager. Just enter
devmgmt.mscin the Windows search bar, console, or PowerShell to open it.
Since this is a Plug & Play driver, there is no need to reboot the machine.