For the complete documentation index, see llms.txt. This page is also available as Markdown.

Service description

Version 2026.10.27


Block Storage provides persistent block storage for KVM virtual machines in Glesys Cloud. Storage volumes are managed separately from the virtual machine's local system disk.

Choose between three performance tiers — Capacity, Balanced, and Velocity — and provision storage capacity based on your requirements. Volumes can be expanded while the virtual machine is running, detached, and attached to another KVM virtual machine.

Block Storage volumes remain available even if the virtual machine they were attached to is deleted. Learn more

Regional availability

Block Storage is available in the following location:

  • dc-fbg1 (our Falkenberg DC, Sweden)

Technical specification

Block Storage is available for KVM virtual machines in Glesys Cloud. Each Block Storage volume is provided as an external raw block device and is managed separately from the virtual machine's local system disk.

Specification
Capacity
Balanced
Velocity

Customer self-service

Yes, managed in the control panel

Yes, managed in the control panel

Yes, managed in the control panel

Minimum volume size

1 GiB

1 GiB

1 GiB

Maximum volume size

2,048 GiB

2,048 GiB

2,048 GiB

Read IOPS

Up to 1,200

Up to 12,000

Up to 120,000

Write IOPS

Up to 1,200

Up to 12,000

Up to 30,000

Block size

4 KiB

4 KiB

4 KiB

Increase volume while VM is running

Yes

Yes

Yes

Volume downsizing

No

No

No

Hot add

Yes

Yes

Yes

Hot remove

Yes

Yes

Yes

Move between KVM virtual machines

Yes

Yes

Yes

Raw block device

Yes

Yes

Yes

Snapshots

No

No

No

Glesys Backup

No

No

No

A KVM virtual machine can have a maximum of 25 drives attached in total. This limit includes Block Storage volumes and other drives attached to the virtual machine.

Performance

The specified IOPS values are up-to limits and are not guaranteed performance levels.

Volume size does not affect the IOPS limits. IOPS limits are determined by the selected performance tier — Capacity, Balanced, or Velocity — regardless of the provisioned volume size.

The performance tier of an existing Block Storage volume cannot currently be changed through the control panel.

Supported operating systems

Hot add and hot remove are supported for the following operating systems and versions:

Operating system
Hot add
Hot remove

Ubuntu 18.04 and later

Yes

Yes

Debian 10 and later

Yes

Yes

AlmaLinux

Yes

Yes

Talos

Yes

Yes

Windows Server 2022 and later

Yes

Yes

OPNsense

Yes

Yes

Volume configuration

Block Storage volumes are provided as raw block devices.

Glesys does not create or manage the filesystem or partition table on the volume. The customer is responsible for creating the required filesystem and, where applicable, partition table, and for mounting the volume in the operating system.

Each Block Storage volume has a unique World Wide Name (WWN). The WWN can be used to identify the corresponding block device inside the virtual machine.

For instructions on identifying, formatting, and mounting a Block Storage volume, see the Block Storage documentation.

Block Storage volumes are managed independently from the virtual machine. If a virtual machine is deleted, an attached Block Storage volume is automatically detached and remains available for use with another virtual machine.

Attaching, detaching and moving volumes

Block Storage volumes can be attached to and detached from KVM virtual machines. For the operating systems listed above, volumes can be added and removed while the virtual machine is running.

A Block Storage volume can only be attached to one KVM virtual machine at a time. To move a volume to another virtual machine, it must first be detached from the current virtual machine before it can be attached to another.

Before detaching or moving a Block Storage volume, ensure that applications are no longer writing to the volume and that it has been safely unmounted or ejected from the operating system.

For step-by-step instructions, see the guides on detaching a Block Storage volume and moving a Block Storage volume between virtual machines.

Resizing volumes

Block Storage supports increasing the size of a volume while the virtual machine is running.

After increasing a volume, the customer is responsible for extending the partition and/or filesystem inside the operating system where required.

Downsizing an existing Block Storage volume is not supported. To reduce the volume size, create a new, smaller Block Storage volume and copy the required data from the existing volume.

Before deleting the original volume, the customer is responsible for verifying that all required data has been successfully copied to the new volume and is accessible.

For step-by-step instructions, see the guide for resizing a Block Storage volume.

Responsibilities

Block Storage infrastructure and platform operation

Glesys

Selecting performance tier and volume size

Customer

Attaching, detaching and moving volumes

Customer

Partitioning and filesystem management

Customer

Mounting and unmounting volumes

Customer

Extending partitions and/or filesystems after a volume increase

Customer

Operating system and application configuration

Customer

Backup of data stored on Block Storage

Customer

Snapshots are not currently available for Block Storage volumes. Glesys Backup does not currently support Block Storage volumes.

Billing

Block Storage is priced per GB per month based on the selected performance tier and provisioned storage capacity. Performance within the specified IOPS limits is included in the price.

Block Storage volumes are billed separately from virtual machines. If a virtual machine is deleted, any attached Block Storage volumes remain available and billing continues until the volumes themselves are deleted.

Block Storage follows Glesys' standard cloud billing model.

Last updated

Was this helpful?