This is the multi-page printable view of this section. Click here to print.
Virtual Server
- 1: Overview
- 1.1: Server Type
- 1.2: Monitoring Metrics
- 1.3: ServiceWatch Metrics
- 2: How-to guides
- 2.1: Image
- 2.2: Keypair
- 2.3: Server Group
- 2.4: Change IP
- 2.5: Configure Linux NTP
- 2.6: Configure RHEL Repo and WKMS
- 2.7: Install ServiceWatch Agent
- 3: API Reference
- 4: CLI Reference
- 5: Release Note
1 - Overview
Service Overview
Virtual Server is a cloud computing-optimized virtual server that lets you freely allocate the amount you need at the required time without having to purchase infrastructure resources such as CPU and memory individually. In a cloud environment, you can use resources with optimized performance according to your computing purpose, such as development, testing, and application execution.
Features
Easy and convenient computing environment setup: Through a web-based Console, users can easily perform self-service provisioning of Virtual Servers, as well as resource and cost management. If you need to change the capacity of major resources such as CPU or Memory while using a Virtual Server, you can easily scale up or down without operator intervention.
Providing various types of services: Provides virtualized vCore/Memory resources according to predefined server types (1~128 vCore).
- General Virtual Server: Provides commonly used computing specs (up to 16 vCore, 256 GB)
- High-capacity Virtual Server: Provided when resources larger than the standard Virtual Server spec are needed.
Strong Security Implementation: By using the Security Group service, you can control inbound/outbound traffic communicating with the external Internet or other VPCs (Virtual Private Cloud) to securely protect the server. Additionally, real-time monitoring enables stable operation of computing resources.
Service Architecture Diagram
Provided features
Virtual Server provides the following features.
- Auto Provisioning and Management: Provides Virtual Server provisioning, resource management, and cost management functions through a web-based Console. If you need to change the capacity of major resources such as CPU or Memory while using Virtual Server, you can modify the server type immediately using the server type modification feature.
- Standard Server Types and Image Provision: Provides virtualized vCore/Memory resources according to standard server types, and offers standard OS images.
- Storage Connection: Provides additional attached storage beyond the OS disk. Block Storage, File Storage, and Object Storage can be attached and used.
- Network Connection: You can connect the standard subnet/IP settings of the Virtual Server and the Public NAT IP. Provides a local subnet connection for inter-server communication. This can be modified on the detail page.
- Security Group Application: Use the Security Group service to control inbound and outbound traffic communicating with external internet or other VPCs, thereby securely protecting the server.
- Monitoring: You can view monitoring information for computing resources such as CPU, Memory, and Disk through the Cloud Monitoring service.
- Backup and Recovery: You can back up and restore the Virtual Server Image using the Backup service.
- Cost Management: You can create, stop, or terminate servers as needed, and since billing is based on actual usage time, you can monitor costs according to consumption.
- ServiceWatch Service Integration: You can monitor data using the ServiceWatch service.
Component
Virtual Server provides standard server types and standard OS images. Users can select and use them according to the desired service scale.
Image
You can create and manage images. The main features are as follows.
- Image creation: You can create an Image from the configuration of a Virtual Server you are using, and you can also create an Image by uploading your Image file to Object Storage.
- Create Shared Image: You can create an Image with Visibility set to Private as a Shared Image that can be shared.
- Share with another Account: You can share the Image with another Account.
- Refer to the How-to guides > Image document for how to create and use images.
Keypair
To ensure a more secure OS login, we strengthen security by providing a Key Pair instead of the ID/Password entry method. The main features are as follows.
- Keypair creation: Generate a user credential to connect to the Virtual Server.
- Retrieve Public Key: You can load a file or manually enter the public key to retrieve it.
- Refer to the How-to guides > Keypair document for creating and using keypairs.
Server Group
Through Server Group settings, you can position the Block Storage added when creating a Virtual Server close to or distributed across racks and hosts. The main features are as follows.
- Server Group Creation: You can set Virtual Servers belonging to the same Server Group as Anti-Affinity(Distributed placement), Affinity(Proximate placement), or Partition(Virtual Server and Block Storage distributed placement).
- Refer to the How-to guides > Server Group document for how to create and use Server Groups.
OS Image provided version
The OS images provided by Virtual Server are as follows
| OS Image version | EoS Date |
|---|---|
| Alma Linux 8.10 | 2029-05-31 |
| Alma Linux 9.6 | 2025-11-17 |
| Oracle Linux 8.10 | 2029-07-31 |
| Oracle Linux 9.6 | 2025-11-25 |
| RHEL 8.10 | 2029-05-31 |
| RHEL 9.4 | 2026-04-30 |
| RHEL 9.6 | 2027-05-31 |
| Rocky Linux 8.10 | 2029-05-31 |
| Rocky Linux 9.6 | 2025-11-30 |
| Ubuntu 22.04 | 2027-06-30 |
| Ubuntu 24.04 | 2029-06-30 |
| Windows 2019 | 2029-01-09 |
| Windows 2022 | 2031-10-14 |
| Windows 2016 | 2027-01-12 |
- Linux operating systems such as Alma Linux and Rocky Linux provide only even Minor versions, except for the final release of a Major version. This policy ensures the stability and consistency of the SCP system. We recommend checking the EOS (End of Support) and EOL (End of Life) dates for the operating system, and, if necessary, applying new or additional individual packages to maintain a stable environment.
Server type
The server types supported by Virtual Server are as follows. For detailed information about server types, see Virtual Server Server Types.
Standard s1v2m4
Category | example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server type classifications
|
| Server specifications | s1 | Provided server type classification and generation
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
Constraints
- When creating a Virtual Server with Rocky Linux or Oracle Linux, additional configuration is required for time synchronization (NTP: Network Time Protocol). For other images, it is set automatically and no separate configuration is needed.
For more details, refer to Linux NTP Setup. - If you created RHEL and Windows Server before August 2025, you need to modify the RHEL Repository and WKMS (Windows Key Management Service) settings.
For more details, see RHEL Repo and WKMS Configuration.
Preliminary Service
This is a list of services that need to be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.
| Service Category | service | Detailed description |
|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment |
| Networking | Security Group | Virtual firewall that controls server traffic |
1.1 - Server Type
Virtual Server server type
Virtual Server provides server types that match the intended use. Server types consist of various combinations such as CPU, Memory, and Network Bandwidth. The host server used for a Virtual Server is determined by the server type selected when creating the Virtual Server. Please choose a server type based on the specifications of the application you plan to run on the Virtual Server.
The server types supported by Virtual Server are as follows.
Standard s1v2m4
Category | example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server type classifications
|
| Server specifications | s1 | Provided server type classification and generation
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
s1 server type
The s1 server type of Virtual Server is offered with standard specifications (vCPU, Memory) and is suitable for various applications.
- First generation of Samsung Cloud Platform v2: Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor with up to 3.3 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | s1v1m2 | 1 vCore | 2 GB | Up to 10 Gbps |
| Standard | s1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | s1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | s1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | s1v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | s1v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | s1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | s1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | s1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | s1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | s1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | s1v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | s1v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | s1v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | s1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | s1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | s1v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | s1v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | s1v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | s1v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | s1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | s1v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | s1v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | s1v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | s1v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | s1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | s1v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | s1v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | s1v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | s1v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | s1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | s1v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | s1v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | s1v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | s1v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | s1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | s1v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | s1v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | s1v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | s1v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | s1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
s2 server type
The Virtual Server s2 server type is offered with standard specifications (vCPU, Memory) and is suitable for various applications.
- Samsung Cloud Platform v2, 2nd generation: Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | CPU vCore | Memory | Network Bandwidth(Gbps) |
|---|---|---|---|---|
| Standard | s2v1m2 | 1 vCore | 2 GB | Up to 10 Gbps |
| Standard | s2v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | s2v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | s2v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | s2v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | s2v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | s2v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | s2v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | s2v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | s2v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | s2v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | s2v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | s2v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | s2v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | s2v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | s2v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | s2v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | s2v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | s2v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | s2v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | s2v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | s2v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | s2v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | s2v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | s2v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | s2v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | s2v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | s2v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | s2v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | s2v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | s2v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | s2v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | s2v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | s2v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | s2v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | s2v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | s2v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | s2v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | s2v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | s2v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | s2v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
h2 Server Type
The h2 server type of Virtual Server is offered with high-capacity specifications and is suitable for applications that require large-scale data processing.
- Second generation of Samsung Cloud Platform v2: Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H processor up to 3.2 GHz
- Supports up to 128 vCPUs and 1,536 GB of memory
- Networking speed up to 25 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| High Capacity | h2v24m48 | 24 vCore | 48 GB | Up to 25 Gbps |
| High Capacity | h2v24m96 | 24 vCore | 96 GB | Maximum 25 Gbps |
| High Capacity | h2v24m192 | 24 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | h2v24m288 | 24 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | h2v32m64 | 32 vCore | 64 GB | Maximum 25 Gbps |
| High Capacity | h2v32m128 | 32 vCore | 128 GB | Maximum 25 Gbps |
| High Capacity | h2v32m256 | 32 vCore | 256 GB | Maximum 25 Gbps |
| High Capacity | h2v32m384 | 32 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | h2v48m96 | 48 vCore | 96 GB | Maximum 25 Gbps |
| High Capacity | h2v48m192 | 48 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | h2v48m384 | 48 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | h2v48m576 | 48 vCore | 576 GB | Maximum 25 Gbps |
| High Capacity | h2v64m128 | 64 vCore | 128 GB | Maximum 25 Gbps |
| High Capacity | h2v64m256 | 64 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | h2v64m512 | 64 vCore | 512 GB | Maximum 25 Gbps |
| High Capacity | h2v64m768 | 64 vCore | 768 GB | Maximum 25 Gbps |
| High Capacity | h2v72m144 | 72 vCore | 144 GB | Up to 25 Gbps |
| High Capacity | h2v72m288 | 72 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | h2v72m576 | 72 vCore | 576 GB | Maximum 25 Gbps |
| High Capacity | h2v72m864 | 72 vCore | 864 GB | Maximum 25 Gbps |
| High Capacity | h2v96m192 | 96 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | h2v96m384 | 96 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | h2v96m768 | 96 vCore | 768 GB | Maximum 25 Gbps |
| High Capacity | h2v96m1152 | 96 vCore | 1152 GB | Maximum 25 Gbps |
| High Capacity | h2v128m256 | 128 vCore | 256 GB | Maximum 25 Gbps |
| High Capacity | h2v128m512 | 128 vCore | 512 GB | Maximum 25 Gbps |
| High Capacity | h2v128m1024 | 128 vCore | 1024 GB | Up to 25 Gbps |
| High Capacity | h2v128m1536 | 128 vCore | 1536 GB | Maximum 25 Gbps |
1.2 - Monitoring Metrics
According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be discontinued in September 2026.
Starting after the September 2026 release, resource monitoring of the Samsung Cloud Platform via Cloud Monitoring will no longer be possible.
With the new alternative service, you can continuously perform resource monitoring by leveraging ServiceWatch released in October 2025.
ServiceWatch provides more modern and powerful features, replacing Cloud Monitoring to deliver a seamless monitoring environment.
Detailed information about ServiceWatch can be found in the ServiceWatch Overview.
Virtual Server Monitoring Metrics
The table below shows the monitoring metrics of Virtual Server that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
Provides basic monitoring metrics even without installing an agent, as shown below table. Please check the Virtual Server monitoring metrics (default). Additionally, the metrics that can be viewed by installing the Agent are in the table below. Virtual Server additional monitoring metrics (Agent installation required)** Please refer to it.
For Windows OS, memory-related metrics can only be viewed after installing the Agent.
| Performance items | Detailed description | unit |
|---|---|---|
| Memory Total [Basic] | bytes of usable memory | bytes |
| Memory Used [Basic] | Current memory usage in bytes | bytes |
| Memory Swap In [Basic] | bytes of the replaced memory | bytes |
| Memory Swap Out [Basic] | bytes of the replaced memory | bytes |
| Memory Free [Basic] | bytes of unused memory | bytes |
| Disk Read Bytes [Basic] | Read bytes | bytes |
| Disk Read Requests [Basic] | Number of read requests | cnt |
| Disk Write Bytes [Basic] | write bytes | bytes |
| Disk Write Requests [Basic] | Number of write requests | cnt |
| CPU Usage [Basic] | Average system CPU usage over 1 minute | % |
| Instance State [Basic] | Instance status | state |
| Network In Bytes [Basic] | Received bytes | bytes |
| Network In Dropped [Basic] | Incoming packet drop | cnt |
| Network In Packets [Basic] | Number of received packets | cnt |
| Network Out Bytes [Basic] | sent bytes | bytes |
| Network Out Dropped [Basic] | Transmit packet drop | cnt |
| Network Out Packets [Basic] | Number of transmitted packets | cnt |
| Performance items | Detailed description | unit |
|---|---|---|
| Core Usage [IO Wait] | Ratio of CPU time spent in wait state (disk wait) | % |
| Core Usage [System] | Proportion of CPU time spent in kernel space | % |
| Core Usage [User] | Proportion of CPU time spent in user space | % |
| CPU Cores | Number of CPU cores on the host | cnt |
| CPU Usage [Active] | Percentage of CPU time used other than Idle and IOWait states | % |
| CPU Usage [Idle] | It is the proportion of CPU time spent in idle state. | % |
| CPU Usage [IO Wait] | This is the proportion of CPU time spent in a waiting state (disk wait). | % |
| CPU Usage [System] | Percentage of CPU time used by the kernel | % |
| CPU Usage [User] | Percentage of CPU time used in user space | % |
| CPU Usage/Core [Active] | Percentage of CPU time used other than Idle and IOWait states | % |
| CPU Usage/Core [Idle] | It is the proportion of CPU time spent in idle state. | % |
| CPU Usage/Core [IO Wait] | This is the proportion of CPU time spent in a waiting state (disk wait). | % |
| CPU Usage/Core [System] | Percentage of CPU time used by the kernel | % |
| CPU Usage/Core [User] | Percentage of CPU time used in user space | % |
| DiskCPU Usage [IO Request] | Proportion of CPU time during which I/O requests to the device were executed | % |
| Disk Queue Size [Avg] | The average queue length of requests executed for the device. | num |
| Disk Read Bytes | The number of bytes read per second from the device. | bytes |
| Disk Read Bytes [Delta Avg] | Average of system.diskio.read.bytes_delta for individual disks | bytes |
| Disk Read Bytes [Delta Max] | Maximum system.diskio.read.bytes_delta of individual disks | bytes |
| Disk Read Bytes [Delta Min] | Minimum of system.diskio.read.bytes_delta for individual disks | bytes |
| Disk Read Bytes [Delta Sum] | Sum of system.diskio.read.bytes_delta of individual disks | bytes |
| Disk Read Bytes [Delta] | Delta of the system.diskio.read.bytes value for each Disk | bytes |
| Disk Read Bytes [Success] | Total bytes successfully read | bytes |
| Disk Read Requests | Number of read requests to the disk device per second | cnt |
| Disk Read Requests [Delta Avg] | Average of system.diskio.read.count_delta for individual disks | cnt |
| Disk Read Requests [Delta Max] | Maximum system.diskio.read.count_delta for individual disks | cnt |
| Disk Read Requests [Delta Min] | Minimum of system.diskio.read.count_delta for individual disks | cnt |
| Disk Read Requests [Delta Sum] | Sum of the system.diskio.read.count_delta of individual disks | cnt |
| Disk Read Requests [Success Delta] | Delta of system.diskio.read.count for each Disk | cnt |
| Disk Read Requests [Success] | Total number of successful reads | cnt |
| Disk Request Size [Avg] | It is the average size of requests executed on the device (unit: sectors). | num |
| Disk Service Time [Avg] | Average service time (milliseconds) of input requests executed on the device. | ms |
| Disk Wait Time [Avg] | Average time taken for requests executed on the supported device. | ms |
| Disk Wait Time [Read] | Average disk wait time | ms |
| Disk Wait Time [Write] | Average disk wait time | ms |
| Disk Write Bytes [Delta Avg] | Average of system.diskio.write.bytes_delta for each disk | bytes |
| Disk Write Bytes [Delta Max] | Maximum system.diskio.write.bytes_delta of individual disks | bytes |
| Disk Write Bytes [Delta Min] | Minimum of system.diskio.write.bytes_delta for individual disks | bytes |
| Disk Write Bytes [Delta Sum] | Sum of system.diskio.write.bytes_delta for individual disks | bytes |
| Disk Write Bytes [Delta] | Delta of the system.diskio.write.bytes value for each Disk | bytes |
| Disk Write Bytes [Success] | Total number of bytes successfully written | bytes |
| Disk Write Requests | Number of write requests to the disk device per second | cnt |
| Disk Write Requests [Delta Avg] | Average of system.diskio.write.count_delta for individual disks | cnt |
| Disk Write Requests [Delta Max] | Maximum system.diskio.write.count_delta of individual disks | cnt |
| Disk Write Requests [Delta Min] | Minimum of system.diskio.write.count_delta for individual disks | cnt |
| Disk Write Requests [Delta Sum] | Sum of system.diskio.write.count_delta for individual disks | cnt |
| Disk Write Requests [Success Delta] | Delta of system.diskio.write.count for each Disk | cnt |
| Disk Write Requests [Success] | Total number of successful writes | cnt |
| Disk Writes Bytes | Bytes per second written to the device | bytes |
| Filesystem Hang Check | filesystem(local/NFS) hang check(normal:1, abnormal:0) | status |
| Filesystem Nodes | Total number of file nodes in the file system. | cnt |
| Filesystem Nodes [Free] | It is the total number of available file nodes in the file system. | cnt |
| Filesystem Size [Available] | Disk space (bytes) available to unauthorized users | bytes |
| Filesystem Size [Free] | Available disk space (bytes) | bytes |
| Filesystem Size [Total] | Total disk space (bytes) | bytes |
| Filesystem Usage | Used disk space percentage | % |
| Filesystem Usage [Avg] | Average of individual filesystem.used.pct | % |
| Filesystem Usage [Inode] | iNode usage rate | % |
| Filesystem Usage [Max] | Maximum among individual filesystem.used.pct | % |
| Filesystem Usage [Min] | Min among individual filesystem.used.pct | % |
| Filesystem Usage [Total] | - | % |
| Filesystem Used | Used disk space (bytes) | bytes |
| Filesystem Used [Inode] | iNode usage | bytes |
| Memory Free | Total available memory (bytes) | bytes |
| Memory Free [Actual] | Actual usable Memory (bytes) | bytes |
| Memory Free [Swap] | Available Swap memory | bytes |
| Memory Total | Total Memory | bytes |
| Memory Total [Swap] | Total Swap memory. | bytes |
| Memory Usage | Percentage of used memory | % |
| Memory Usage [Actual] | Percentage of memory actually used | % |
| Memory Usage [Cache Swap] | cached swap usage | % |
| Memory Usage [Swap] | Percentage of used Swap memory | % |
| Memory Used | Used Memory | bytes |
| Memory Used [Actual] | Actual memory used (bytes) | bytes |
| Memory Used [Swap] | Used Swap memory | bytes |
| Collisions | Network collision | cnt |
| Network In Bytes | Number of received bytes | bytes |
| Network In Bytes [Delta Avg] | Average of system.network.in.bytes_delta for individual networks | bytes |
| Network In Bytes [Delta Max] | Maximum system.network.in.bytes_delta for each Network | bytes |
| Network In Bytes [Delta Min] | Minimum of system.network.in.bytes_delta for each network | bytes |
| Network In Bytes [Delta Sum] | Sum of system.network.in.bytes_delta for individual networks | bytes |
| Network In Bytes [Delta] | Delta of received byte count | bytes |
| Network In Dropped | Number of deleted packets among incoming packets | cnt |
| Network In Errors | Number of errors during reception | cnt |
| Network In Packets | Number of received packets | cnt |
| Network In Packets [Delta Avg] | Average of system.network.in.packets_delta for individual Networks | cnt |
| Network In Packets [Delta Max] | Maximum of system.network.in.packets_delta for each Network | cnt |
| Network In Packets [Delta Min] | Minimum of system.network.in.packets_delta for each Network | cnt |
| Network In Packets [Delta Sum] | Sum of system.network.in.packets_delta for individual Networks | cnt |
| Network In Packets [Delta] | Delta of received packet count | cnt |
| Network Out Bytes | Number of transmitted bytes | bytes |
| Network Out Bytes [Delta Avg] | Average of system.network.out.bytes_delta for individual networks | bytes |
| Network Out Bytes [Delta Max] | Maximum system.network.out.bytes_delta for each Network | bytes |
| Network Out Bytes [Delta Min] | Minimum of system.network.out.bytes_delta for individual Networks | bytes |
| Network Out Bytes [Delta Sum] | Sum of system.network.out.bytes_delta for individual Networks | bytes |
| Network Out Bytes [Delta] | Delta of transmitted byte count | bytes |
| Network Out Dropped | Number of deleted packets among outgoing packets | cnt |
| Network Out Errors | Number of errors during transmission | cnt |
| Network Out Packets | Number of transmitted packets | cnt |
| Network Out Packets [Delta Avg] | Average of system.network.out.packets_delta for each Network | cnt |
| Network Out Packets [Delta Max] | Maximum system.network.out.packets_delta for each Network | cnt |
| Network Out Packets [Delta Min] | Minimum of system.network.out.packets_delta for each Network | cnt |
| Network Out Packets [Delta Sum] | Sum of system.network.out.packets_delta for individual networks | cnt |
| Network Out Packets [Delta] | Delta of transmitted packet count | cnt |
| Open Connections [TCP] | All open TCP connections | cnt |
| Open Connections [UDP] | All open UDP connections | cnt |
| Port Usage | Connectable port utilization | % |
| SYN Sent Sockets | Number of sockets in SYN_SENT state (when connecting from local to remote) | cnt |
| Kernel PID Max | kernel.pid_max value | cnt |
| Kernel Thread Max | kernel.threads-max value | cnt |
| Process CPU Usage | Percentage of CPU time consumed by the process since the last update | % |
| Process CPU Usage/Core | Percentage of CPU time used by the process since the last event | % |
| Process Memory Usage | Proportion of main memory (RAM) occupied by a process | % |
| Process Memory Used | Resident Set size. The amount of memory a process occupies in RAM. | bytes |
| Process PID | process pid | pid |
| Process PPID | Parent process PID | pid |
| Processes [Dead] | Number of deadProcesses | cnt |
| Processes [Idle] | idle Processes count | cnt |
| Processes [Running] | running Processes count | cnt |
| Processes [Sleeping] | sleeping processes count | cnt |
| Processes [Stopped] | stopped processes count | cnt |
| Processes [Total] | Total number of processes | cnt |
| Processes [Unknown] | Number of processes whose status cannot be retrieved or is unknown | cnt |
| Processes [Zombie] | Number of zombie processes | cnt |
| Running Process Usage | process usage | % |
| Running Processes | Number of running processes | cnt |
| Running Thread Usage | Thread usage rate | % |
| Running Threads | Total number of threads running in running processes | cnt |
| Context Switches | context switch count (per second) | cnt |
| Load/Core [1 min] | The load over the last 1 minute divided by the number of cores | cnt |
| Load/Core [15 min] | The load over the last 15 minutes divided by the number of cores | cnt |
| Load/Core [5 min] | The load over the last 5 minutes divided by the number of cores | cnt |
| Multipaths [Active] | External storage connection path status = active count | cnt |
| Multipaths [Failed] | External storage connection path status = failed count | cnt |
| Multipaths [Faulty] | External storage connection path status = faulty count | cnt |
| NTP Offset last | sample’s measured offset (time difference between NTP server and local environment) | num |
| Run Queue Length | Execution queue length | num |
| Uptime | OS uptime (milliseconds) | ms |
| Context Switchies CPU | context switch count (per second) | cnt |
| Disk Read Bytes [Sec] | Number of bytes read in one second from a Windows logical disk
| cnt |
| Disk Read Time [Avg] | Data read average time (seconds)
| sec |
| Disk Transfer Time [Avg] | Disk average wait time (seconds)
| sec |
| Disk Write Bytes [Sec] | Number of bytes written in one second on a Windows logical disk
| cnt |
| Disk Write Time [Avg] | Average data write time (seconds)
| sec |
| Pagingfile Usage | paging file usage
| % |
| Pool Used [Non Paged] | Nonpaged Pool usage in kernel memory
| bytes |
| Pool Used [Paged] | Paged Pool usage in kernel memory
| bytes |
| Process [Running] | Number of currently running processes
| cnt |
| Threads [Running] | Number of currently running threads
| cnt |
| Threads [Waiting] | Number of threads waiting for processor time
| cnt |
1.3 - ServiceWatch Metrics
Virtual Server sends metrics to ServiceWatch. The metrics provided by default monitoring are data collected at 5‑minute intervals. If detailed monitoring is enabled, you can view data collected at 1‑minute intervals.
See How-to guides > ServiceWatch Enable Detailed Monitoring for instructions on enabling detailed monitoring of Virtual Server.
Basic Metrics
The following are the basic metrics for the Virtual Server namespace.
The indicators whose names are displayed in bold below are the indicators selected as key metrics among the default metrics provided by Virtual Server. The key metrics are used to build service dashboards that are automatically generated for each service in ServiceWatch. They can also be viewed on the Monitoring tab of the Virtual Server detail page.
Each metric provides guidance in the user guide on which statistical value is meaningful to query, and among the meaningful statistics, the values shown in bold text are the primary statistics. In the service dashboard or monitoring tab, you can view primary metrics using these primary statistics.
| Performance item (indicator name) | Detailed description | unit | meaningful statistics | |
|---|---|---|---|---|
| Instance State | Instance status display
| None |
| |
| CPU Usage | CPU usage | Percent |
| |
| Disk Read Bytes | Bytes read from block device (bytes) | Bytes |
| |
| Disk Read Requests | Number of read requests on a block device | Count |
| |
| Disk Write Bytes | Write capacity (bytes) on block device | Bytes |
| |
| Disk Write Requests | Number of write requests on block device | Count |
| |
| Network In Bytes | Received bytes on the network interface | Bytes |
| |
| Network In Dropped | Number of packet drops received on the network interface | Count |
| |
| Network In Packets | Number of packets received on the network interface | Count |
| |
| Network Out Bytes | Data transmitted on the network interface (bytes) | Bytes |
| |
| Network Out Dropped | Number of packet drops transmitted from the network interface | Count |
| |
| Network Out Packets | Number of packets transmitted on the network interface | Count |
|
2 - How-to guides
Users can create the service by entering the required information for a Virtual Server and selecting detailed options through the Samsung Cloud Platform Console.
Create Virtual Server
You can create and use a Virtual Server service in the Samsung Cloud Platform Console.
To create a Virtual Server, follow these steps.
Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
On the Service Home page, click the Create Virtual Server button. 2. Navigate to the Create Virtual Server page.
On the Virtual Server Creation page, enter the information required to create the service and select detailed options.
- Select the required information in the Image and version selection area.
Category required statusDetailed description Image Required Select the provided Image type - Standard: Samsung Cloud Platform standard provided Image
- Alma Linux, Oracle Linux, RHEL, Rocky Linux, Ubuntu, Windows
- Custom: User-created Image
- Kubernetes: Image for Kubernetes
- RHEL, Ubuntu
- Marketplace: Image subscribed from Marketplace
Image version Required Select version of the selected Image - Provide version list of the server Image
Table. Virtual Server Image and version selection input items - Standard: Samsung Cloud Platform standard provided Image
- In the Service Information Input area, enter or select the required information.
Category required statusDetailed description Number of servers Required Number of servers to create concurrently - Only numeric input is allowed, and enter a value between 1~100
Service Type > Server Type Required Virtual Server server type - Standard: standard specifications commonly used
- High Capacity: large‑capacity server specifications beyond Standard
- For detailed information about the server types provided by Virtual Server, see Virtual Server 서버 타입
Service Type > Planned Compute Required Planned Compute-configured resource status - In Use: Number of resources with Planned Compute that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Apply for Planned Compute Service: Go to the Planned Compute service creation page
- For more details, refer to Planned Compute Apply
Block Storage Essential Block Storage settings used by the server according to purpose - Basic OS: Area where the OS is installed and used
- Capacity is entered in Units, and the minimum size varies by OS Image type
- Alma Linux: Enter a value between 2~1,536
- Oracle Linux: Enter a value between 7~1,536
- RHEL: Enter a value between 2~1,536
- Rocky Linux: Enter a value between 2~1,536
- Ubuntu: Enter a value between 2~1,536
- Windows: Enter a value between 4~1,536
- SSD: High‑performance general volume
- HDD: General volume
- SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management Service) encryption keys
- Encryption can be applied only at initial creation and cannot be changed afterward
- Using the SSD_KMS disk type may cause performance degradation
- SSD_Provisioned: SSD volume with configurable IOPS and Throughput
- Capacity is entered in Units, and the minimum size varies by OS Image type
- Additional: Used when extra user space beyond the OS area is needed
- After selecting Use, enter the storage type and capacity
- To add storage, click the + button; to delete, click the x button (up to 25 can be added)
- Capacity is entered in Units, with a value between 1~1,536
- 1 Unit equals 8 GB, so 8~12,288 GB are created
- SSD: High‑performance general volume
- HDD: General volume
- SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management Service) encryption keys
- Encryption can be applied only at initial creation and cannot be changed afterward
- Using the SSD_KMS disk type may cause performance degradation
- SSD/HDD_MultiAttach: Volume that can be attached to two or more servers
- SSD_Provisioned: SSD volume with configurable IOPS and Throughput
- For details on each Block Storage type, see Block Storage 생성하기
- Delete on termination: When Delete on Termination is selected, the volume is terminated together with the server
- A volume with an existing snapshot is not deleted even when Delete on termination is enabled
- A multi‑attach volume can be deleted only when the server being removed is the last remaining server attached to the volume
- Max IOPS: Enter a maximum IOPS value between 5,000~20,000
- Not configurable for disk types HDD, HDD_KMS, HDD_MultiAttach
- Max Throughput: Enter a maximum Throughput value between 250~1,000
- Not configurable for disk types HDD, HDD_KMS, HDD_MultiAttach
Server Group Select After selecting Use for setting Anti-Affinity (distributed placement), Affinity (proximate placement), Partition (distributed placement of Virtual Server and Block Storage) for servers belonging to the same Server Group - , select the Server Group
- , choose Create New to create the Server Group
Servers belonging to the same Server Group are placed in a Best Effort manner according to the selected policy The policy can be selected among Anti-Affinity (distributed placement), Affinity (proximate placement), Partition (distributed placement of Virtual Server and Block Storage) Table. Virtual Server service information input itemsCautionWhen using the Partition (distributed placement of Virtual Server and Block Storage) policy among Server Group policies, you cannot allocate additional Block Storage Volumes after creating a Virtual Server, so create all required Block Storage during the Virtual Server creation step. - Required Information Input area, please enter or select the required information.
Category required statusDetailed description Server name Essential Enter a name to distinguish the server when the selected number of servers is 1 - Set the hostname to the entered server name
- Enter using English letters, numbers, spaces, and special characters (
-,_) within 63 characters
Network Settings > Create New Network Port Required Set the network where the Virtual Server will be installed - VPC Name: Select a pre‑created VPC
- General Subnet: Select a pre‑created general Subnet
- IP can be set to auto‑generate or user‑provided; if input is selected, the user can manually enter the IP
- NAT: Available only when there is a single server and the VPC is attached to an Internet Gateway. Checking Use allows selection of a NAT IP
- NAT IP: Select a NAT IP
- If no NAT IP is available, click the Create New button to generate a Public IP
- Refresh button to view and select the created Public IP
- Creating a Public IP incurs charges according to the Public IP pricing policy
- Local Subnet (optional): Select Use for a local Subnet
- It is not a required element for creating the service
- A pre‑created local Subnet must be selected
- IP can be set to auto‑generate or user‑provided; if input is selected, the user can manually enter the IP
- Security Group: Settings required to access the server
- Select: Choose a pre‑created Security Group
- Create New: If no applicable Security Group exists, it can be created separately in the Security Group service
- Up to 5 can be selected
- If no Security Group is set, all connections are blocked by default
- A Security Group must be configured to allow required connections
Network Settings > Specify Existing Network Port Required Set the network where the Virtual Server will be installed - VPC: Select a pre‑created VPC
- General Subnet: Select a pre‑created general Subnet and port
- NAT: Available only when there is a single server and the VPC is attached to an Internet Gateway. When enabled, you can select a NAT IP
- NAT IP: Select a NAT IP
- If no NAT IP is available to select, click the Create New button to generate a Public IP
- Refresh button to view and select the created Public IP
- Local Subnet (Optional): Choose Use for the local Subnet
- Select a pre‑created local Subnet and port
Keypair Required User authentication method to use when connecting to the server - Create new: Create a new one if a new keypair is required
- Refer to Keypair 생성하기
- Default login account list by OS
- Alma Linux: almalinux
- Oracle Linux: cloud-user
- RHEL: cloud-user
- Rocky Linux: rocky
- Ubuntu: ubuntu
- Windows: sysadmin
Table: Required input fields for Virtual Server - Additional Information Input area, please enter or select the required information.
Category required statusDetailed description Lock Select Lock usage setting - Using the lock prevents actions such as server termination, start, stop, etc., from being executed, preventing misoperations due to mistakes
Init script Select the script that runs when the server starts - The init script must be written as a Batch script for Windows, a Shell script or cloud‑init for Linux, depending on the Image type.
- Up to 45,000 bytes can be entered
tag Select Add Tag - Up to 50 can be added per resource
- After clicking the Add Tag button, enter or select Key, Value values
Table. Virtual Server additional information input fields
- Select the required information in the Image and version selection area.
Summary Check the detailed information and estimated charges generated in the panel, and click the Create button.
- Once creation is complete, check the created resources on the Virtual Server List page.
- When entering the server name, if spaces and special characters (
_) are used, the OS hostname will have spaces and special characters (_) changed to the special character (-) and be set. * Refer to this when setting the OS hostname.- Example: If the server name is ‘server name_01’, the OS hostname is set to ‘server-name-01’.
- If you need to manage server names uniquely, specify a different server name (Prefix) when creating them.
- When creating a server, because the numbering does not automatically increment based on the server name (Prefix), a Virtual Server with the same name can be created.
- Example: If you first create two Virtual Servers using the server name (Prefix) ’test’, ’test-1’ and ’test-2’ will be created. * After that, even if you create two Virtual Servers again using the prefix ’test’, ’test-1’ and ’test-2’ will be created.
- If you create a Virtual Server with Rocky Linux or Oracle Linux, additional configuration is required for time synchronization (NTP: Network Time Protocol). * For more details, please refer to Linux NTP 설정하기.
- If RHEL and Windows Server were created before July 2025, you need to modify the RHEL Repository and WKMS (Windows Key Management Service) settings. For detailed information, refer to RHEL Repo 및 WKMS 설정하기.
Check Virtual Server detailed information
The Virtual Server service allows you to view and edit the entire resource list and detailed information. The Virtual Server Details page includes the Details, Monitoring, Tags, Activity Log tabs.
To view detailed information about the Virtual Server service, follow these steps.
- All Services > Compute > Virtual Server menu, click it. 1. Navigate to the Service Home page of the Virtual Server.
- On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
- On the Virtual Server List page, click the resource to view detailed information. 3. Navigate to the Virtual Server Details page.
- Virtual Server Details page displays status information and additional feature information, and consists of Details, Monitoring, Tags, Activity Log tabs.
- For detailed information about Virtual Server Add-on Features, please refer to Virtual Server Management Add-on Features.
Category Detailed description Virtual Server status Status of a user-created Virtual Server - Build: State where a Build command has been received
- Building: Build in progress
- Networking: Server creation networking process
- Scheduling: Server creation scheduling process
- Block_Device_Mapping: Attaching Block Storage during server creation
- Spawning: Server creation process is ongoing
- Active: Available state
- Powering_off: State when a shutdown request is made
- Deleting: Server deletion in progress
- Reboot_Started: Reboot in progress
- Error: Error state
- Migrating: Server is being migrated to another host
- Reboot: Reboot command has been received
- Rebooting: Restart in progress
- Rebuild: Rebuild command has been received
- Rebuilding: State when a Rebuild request is made
- Rebuild_Spawning: Rebuild process is ongoing
- Resize: Resize command has been received
- Resizing: Resize in progress
- Resize_Prep: State when a server type change is requested
- Resize_Migrating: Server is being moved to another host while resizing
- Resize_Migrated: Server has completed moving to another host during resize
- Resize_Finish: Resize completed
- Revert_Resize: Resize or migration of the server failed for some reason. The target server is cleaned up and the original server is restarted
- Shutoff: State when powering off is completed
- Verity_ Resize: After a server type change request and Resize_Prep, the server type is confirmed or can be reverted
- Resize_Reverting: State when a server type revert is requested
- Resize_Confirming: State while confirming the server’s Resize request
Server control Buttons to change server status - Start: Start a stopped server
- Stop: Stop a running server
- Restart: Restart a running server
Image generation Create a user Image from the current server’s Image - For detailed Image creation instructions, see Create Image
Console log View console logs of the current server - You can check the console logs output by the current server. For more details, see 콘솔 로그 확인하기
Create dump Create a dump of the current server - Dump file is created inside the Virtual Server
- Refer to Dump 생성하기 for detailed dump creation instructions
Rebuild The OS area data and settings of the existing Virtual Server are deleted, and it is rebuilt on a new server - For details, see Rebuild 수행하기
Service termination Button to cancel the service Table. Virtual Server status information and additional functions
Detailed Information
Virtual Server List page lets you view detailed information of the selected resource and, if needed, modify the information.
| Category | Detailed description |
|---|---|
| service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource name | Resource name
|
| Resource ID | Unique resource ID in the service |
| Constructor | User who created the service |
| Creation date and time | Service creation timestamp |
| Modifier | User who edited the service information |
| Modification timestamp | Date and time the service information was modified |
| Server name | Server name
|
| Server type | vCPU, memory information display
|
| Image name | Server OS Image and version
|
| Lock | Show lock usage status
|
| Server group | Server group name to which the server belongs
|
| Keypair name | Server authentication information set by the user
|
| Planned Compute | Resource status with Planned Compute configured
|
| ServiceWatch detailed monitoring | ServiceWatch detailed monitoring activation status display
|
| Network | Network information of the Virtual Server
|
| Local Subnet | Local Subnet information of the Virtual Server
|
| Block Storage | Server-connected Block Storage information
|
Monitoring
You can monitor the ServiceWatch metrics of the resources selected on the Virtual Server List page. In the Monitoring tab, you can view monitoring charts for the Virtual Server, and each chart is based on the available Service Watch metrics.
| Category | Detailed description |
|---|---|
| Period setting area | Select the period applied to the chart
|
| Time Zone Settings Section | Select time zone for the chart |
| Reset button | Reset all manipulations and settings made on the chart |
| Refresh Settings Area | Select chart refresh interval
|
| Go to the service dashboard | Navigate to the ServiceWatch dashboard list screen |
| More | Display additional tasks for managing charts
|
| graph area | Data graph collected over the chart’s applied period
|
- The metrics provided by basic monitoring are data collected at 5‑minute intervals.
- For detailed information about the ServiceWatch metrics of Virtual Server, refer to Virtual Server ServiceWatch metrics.
Tag
Virtual Server List page lets you view the tag information of the selected resource, and you can add, modify, or delete it.
| Category | Detailed description |
|---|---|
| Tag list | Tag list
|
Job History
Virtual Server List page allows you to view the operation history of the selected resource.
| Category | Detailed description |
|---|---|
| Task History List | Resource Change History
|
Control Virtual Server Operation
If you need to control the operation of a created Virtual Server resource, you can perform the task from the Virtual Server List or Virtual Server Details page. You can start, stop, and restart a running server.
Getting Started with Virtual Server
You can start a Virtual Server that is Shutoff. To start the Virtual Server, follow these steps.
- Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
- On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
- Virtual Server List page, click the resource to start among the shutoff servers, and navigate to the Virtual Server Details page.
- On the Virtual Server List page, you can Start each resource via the right More button.
- After selecting multiple servers with checkboxes, you can control multiple servers simultaneously using the Start button at the top.
- Virtual Server Details page, click the Start button at the top to start the server. 4. Check the status of the modified server in the Status Indicator item.
- When the Virtual Server start is complete, the server status changes from Shutoff to Active.
- For detailed information about the Virtual Server status, please refer to Virtual Server Detailed Information.
Stop Virtual Server
You can stop a Virtual Server that is running (Active). To stop the Virtual Server, follow the steps below.
- Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
- On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
- On the Virtual Server List page, click the resource to stop among the active servers, and proceed to the Virtual Server Details page.
- On the Virtual Server List page, you can stop each resource via the right More button.
- After selecting multiple servers with checkboxes, you can control multiple servers simultaneously using the Stop button at the top.
- On the Virtual Server Details page, click the Stop button at the top to start the server. 4. Check the status of the modified server in the Status Indicator item.
- When the Virtual Server shutdown is complete, the server status changes from Active to Shutoff.
- For detailed information about the Virtual Server status, please refer to Virtual Server Detailed Information.
Restart Virtual Server
You can restart the created Virtual Server. To restart the Virtual Server, follow these steps.
- Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
- On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
- On the Virtual Server List page, click the resource to restart, and go to the Virtual Server Details page.
- On the Virtual Server list page, you can restart each resource via the right More button.
- After selecting multiple servers with checkboxes, you can control multiple servers simultaneously using the Restart button at the top.
- On the Virtual Server Details page, click the Restart button at the top to start the server. 4. Check the status of the changed server in the Status Display section.
- During a Virtual Server restart, the server status goes through Rebooting and finally changes to Active.
- For detailed information about the Virtual Server status, please refer to Virtual Server Detailed Information.
Managing Virtual Server Resources
If you need server control and management functions for the created Virtual Server resources, you can perform tasks on the Virtual Server List or Virtual Server Details page.
Create Image
You can create an image of a running Virtual Server.
This content explains how to create a user image on a running Virtual Server.
- On the Virtual Server list or Virtual Server details page, click the Create Image button to create a user Image.
- Refer to Image Detailed Guide: Creating an Image for the method of creating an Image by uploading an Image file owned by the user.
To create an Image of a Virtual Server, follow these steps.
Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of Virtual Server.
On the Service Home page, click the Virtual Server menu. 2. Navigate to the Virtual Server List page.
On the Virtual Server List page, click the resource to create an Image. 3. Navigate to the Virtual Server Details page.
On the Virtual Server Details page, click the Create Image button. 4. Go to the Image creation page.
- Enter the required information in the Service Information Input area.
Category required statusDetailed description Image name Required the name of the Image to be created - English letters, numbers, spaces, and special characters (
-,_) within 200 characters
Table. Image service information input fields - English letters, numbers, spaces, and special characters (
- Enter the required information in the Service Information Input area.
Check the input information and click the Complete button.
- When creation is complete, check the created resources on the All Services > Compute > Virtual Server > Image List page.
- When an Image is created, the generated Image is stored in the Object Storage used as internal storage. * Therefore, a usage fee will be charged for image storage.
- Since the file system of an Image created from an Active Virtual Server cannot be guaranteed to be intact, it is recommended to stop the server before creating the Image.
Edit Server Type
You can modify the server type of a Virtual Server.
To modify the server type of a Virtual Server, follow these steps.
- Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
- On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
- On the Virtual Server List page, click the resource you want to control. 3. Go to the Virtual Server Details page.
- On the Virtual Server Details page, check the server status and click the Edit button for the server type. 4. Edit Server Type popup window opens.
- Edit Server Type In the popup window, after changing the server type, click the Confirm button.
- If you modify the Virtual Server’s server type, the Virtual Server status changes to a state related to performing a resize.
- For detailed information about the Virtual Server status, please refer to Virtual Server Detailed Information.