# Compute Engine FAQs

This is solely for informational purpose and does not require any action from you. IONOS has renamed **Virtual Server(s)** to **Dedicated Core Server(s)**. This change does not impact the functionality of the product in any manner. As a result, the documentation portal now reflects the product name changes. For more information, see

[Product Renaming FAQs](https://docs.wireddatatechs.com/compute/compute-engine/broken-reference)

.

#### What are the maximum resources available for a Server? <a href="#what-are-the-maximum-resources-available-for-a-server" id="what-are-the-maximum-resources-available-for-a-server"></a>

Dedicated Core 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 Dedicated Core Servers 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.

You can scale up the HDD and SSD storage volumes on need basis.

#### What are the Availability Zones? <a href="#what-are-the-availability-zones" id="what-are-the-availability-zones"></a>

IONOS data centers are divided into separate areas called Availability Zones.

You can enhance reliability and set up high-availability scenarios by deploying redundant Dedicated Core Servers and storage devices across multiple Availability Zones.

#### How do I change the Availability Zone? <a href="#how-do-i-change-the-availability-zone" id="how-do-i-change-the-availability-zone"></a>

* Select the server in the DCD **Workspace**
* Use **Inspector** > **Properties** > **Availability Zone** menu to change the Availability Zone

#### What is Live Vertical Scaling? <a href="#what-is-live-vertical-scaling" id="what-is-live-vertical-scaling"></a>

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.

#### Why do I sometimes see steal time in my Dedicated Core servers? <a href="#why-do-i-sometimes-see-steal-time-in-my-dedicated-core-servers" id="why-do-i-sometimes-see-steal-time-in-my-dedicated-core-servers"></a>

Steal time in a

[Virtual Machine (VM)](https://docs.ionos.com/support/general-information/glossary-of-terms#virtual-machine-vm)

refers to instances when the hypervisor, responsible for managing VMs and hardware, temporarily reallocates a portion of CPU cycles from dedicated cores to perform essential tasks like storage replication and firewall enforcement. While VMs may perceive this as "stolen processing time," it typically has a low impact on performance, especially with Dedicated Core servers. The IONOS Cloud platform prioritizes efficient resource management to ensure your VMs run smoothly.

#### How do I reboot a Dedicated Core server? <a href="#how-do-i-reboot-a-dedicated-core-server" id="how-do-i-reboot-a-dedicated-core-server"></a>

Dedicated Core 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.

#### How do I shut down a Dedicated Core server? <a href="#how-do-i-shut-down-a-dedicated-core-server" id="how-do-i-shut-down-a-dedicated-core-server"></a>

You should use the 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.

#### How do I delete a Dedicated Core server? <a href="#how-do-i-delete-a-dedicated-core-server" id="how-do-i-delete-a-dedicated-core-server"></a>

You can delete a Dedicated Core server from the DCD Workspace by right-clicking on it and selecting **Delete Server** from the list, or by selecting the server and pressing the `Del` key on your keyboard.

#### What do I do when my VM isn't accessible? <a href="#what-do-i-do-when-my-vm-isnt-accessible" id="what-do-i-do-when-my-vm-isnt-accessible"></a>

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 `uptime` and `top`.

#### How do I get the root/admin passwords with IONOS images? <a href="#how-do-i-get-the-root-admin-passwords-with-ionos-images" id="how-do-i-get-the-root-admin-passwords-with-ionos-images"></a>

When using IONOS-provided images, you set the passwords yourself prior to provisioning.

#### Why does my newly provisioned server not start? <a href="#why-does-my-newly-provisioned-server-not-start" id="why-does-my-newly-provisioned-server-not-start"></a>

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.

#### Which CPU architecture should I choose? <a href="#which-cpu-architecture-should-i-choose" id="which-cpu-architecture-should-i-choose"></a>

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.

#### What do I do if the cursor in the Remote Console disappears? <a href="#what-do-i-do-if-the-cursor-in-the-remote-console-disappears" id="what-do-i-do-if-the-cursor-in-the-remote-console-disappears"></a>

When the cursor disappears after logging on to the Remote Console, you can reconnect to the server using the appropriate menu entry.

#### What are the maximum resources available for a vCPU Server? <a href="#what-are-the-maximum-resources-available-for-a-vcpu-server" id="what-are-the-maximum-resources-available-for-a-vcpu-server"></a>

vCPU Server configurations are subject to the following limits:

* Up to 120 cores and 512 GB RAM

A CPU Family of a vCPU server cannot be chosen at the time of creation and cannot be changed later.

A single Intel® physical core with Hyper-Threading Technology is exposed to the operating system of your vCPU 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.

You can scale up the HDD and SSD storage volumes on need basis.

#### What are the Availability Zones? <a href="#what-are-the-availability-zones-1" id="what-are-the-availability-zones-1"></a>

IONOS data centers are divided into separate areas called Availability Zones.

You can enhance reliability and set up high-availability scenarios by deploying redundant vCPU Servers and storage devices across multiple Availability Zones.

#### How do I change the Availability Zone? <a href="#how-do-i-change-the-availability-zone-1" id="how-do-i-change-the-availability-zone-1"></a>

* Select the vCPU Server in the DCD **Workspace**.
* Navigate to the **Inspector** pane > **Properties** > **Availability Zone** menu to change the Availability Zone.

#### What is Live Vertical Scaling? <a href="#what-is-live-vertical-scaling-1" id="what-is-live-vertical-scaling-1"></a>

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.

#### How do I reboot a server? <a href="#how-do-i-reboot-a-server" id="how-do-i-reboot-a-server"></a>

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.

#### How do I shut down a server? <a href="#how-do-i-shut-down-a-server" id="how-do-i-shut-down-a-server"></a>

You should use the 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.

#### How do I delete a server? <a href="#how-do-i-delete-a-server" id="how-do-i-delete-a-server"></a>

You can delete a server from the DCD Workspace by right-clicking on it and selecting **Delete Server** from the list, or by selecting the server and pressing the `Del` key on your keyboard.

#### What do I do when my VM isn't accessible? <a href="#what-do-i-do-when-my-vm-isnt-accessible-1" id="what-do-i-do-when-my-vm-isnt-accessible-1"></a>

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 `uptime` and `top`.

#### How do I get the root/admin passwords with IONOS images? <a href="#how-do-i-get-the-root-admin-passwords-with-ionos-images-1" id="how-do-i-get-the-root-admin-passwords-with-ionos-images-1"></a>

When using IONOS-provided images, you set the passwords yourself prior to provisioning.

#### Why does my newly provisioned server not start? <a href="#why-does-my-newly-provisioned-server-not-start-1" id="why-does-my-newly-provisioned-server-not-start-1"></a>

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.

#### Which CPU architecture should I choose? <a href="#which-cpu-architecture-should-i-choose-1" id="which-cpu-architecture-should-i-choose-1"></a>

A CPU Family of a vCPU server cannot be chosen at the time of creation and cannot be changed later.

#### What do I do if the cursor in the Remote Console disappears? <a href="#what-do-i-do-if-the-cursor-in-the-remote-console-disappears-1" id="what-do-i-do-if-the-cursor-in-the-remote-console-disappears-1"></a>

When the cursor disappears after logging on to the Remote Console, you can reconnect to the server using the appropriate menu entry.

#### What is the PVPanic device for? <a href="#what-is-the-pvpanic-device-for" id="what-is-the-pvpanic-device-for"></a>

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.

#### Do I need to restart the VM to get PVPanic? <a href="#do-i-need-to-restart-the-vm-to-get-pvpanic" id="do-i-need-to-restart-the-vm-to-get-pvpanic"></a>

No, the PVPanic device is plug-and-play. However, installing drivers may require a restart.

#### What happens if Windows VMs complain about an unknown device? <a href="#what-happens-if-windows-vms-complain-about-an-unknown-device" id="what-happens-if-windows-vms-complain-about-an-unknown-device"></a>

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).

#### Are there any risks when enabling the use of PVPanic? <a href="#are-there-any-risks-when-enabling-the-use-of-pvpanic" id="are-there-any-risks-when-enabling-the-use-of-pvpanic"></a>

There are no issues found when enabling pvpanic. However, users cannot 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.

#### Are there any compatibility issues with AMD or Intel processors? <a href="#are-there-any-compatibility-issues-with-amd-or-intel-processors" id="are-there-any-compatibility-issues-with-amd-or-intel-processors"></a>

There are no special requirements or limitations to any components of a virtualized server. Therefore, PVPanic is completely compatible with AMD and Intel processors.

#### Do we support hardware solutions? <a href="#do-we-support-hardware-solutions" id="do-we-support-hardware-solutions"></a>

The PVPanic device is implemented as an ISA device (using IOPORT).

#### Does my Linux image support the Pvpanic device? <a href="#does-my-linux-image-support-the-pvpanic-device" id="does-my-linux-image-support-the-pvpanic-device"></a>

Check the kernel config `CONFIG_PVPANIC` parameter.

root\@debian:\~# grep --color CONFIG\_PVPANIC /boot/config-$(uname -r)

**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.

#### How do I install the device driver for the pvpanic device on Windows? <a href="#how-do-i-install-the-device-driver-for-the-pvpanic-device-on-windows" id="how-do-i-install-the-device-driver-for-the-pvpanic-device-on-windows"></a>

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).

![](https://1912043049-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-22165f6fcbf12708a1ba5f7a32972ef029299e19%2Fcd_rom.png?alt=media)

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.msc` in 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.
