Errors when creating a VM from a NoOS image

Problem

When creating a virtual machine (VM) from a previously created image, the following errors occur:

Error 1111 Handler throw uncaught exception: vm/host stoi: no conversion;
Error 5111, Repository check failed.

Cause

This incorrect behavior is caused by a bug in the platform code. The issue has been fixed in version 2026.03.1.

The problem occurs when a VM is created from an image based on:

a VM with no operating system installed (NoOS);
a VM whose OS record is marked as deleted in the platform database.

Diagnosis

To confirm the cause of the issue:

Verify the error appears in the web interface. One of the following errors must be present:

#1111 Handler throw uncaught exception: vm/host stoi: no conversion

#5111 Repository check failed

Check which image the VM was created from. The issue is confirmed if either of the following is true:
- the source image came from a VM with no OS (NoOS). To check:
  1. Go to Virtual Machines and select the VM that was used to create the image.
  2. Check the Operating System/Configuration column. If it shows NoOS, the issue is confirmed.
- The OS has been deleted from the platform database. To check whether the image references a deleted OS record:
  1. Connect to the server with the platform via SSH. For more information about connecting via SSH, see Workstation setup.
  2. Connect to the database:
    
    There are potential risks involved in altering a database. We do not recommend making manual edits to the database, as it can disrupt the correct operation of the platform.
    Create a backup of the platform before performing any actions with the database.
    As the platform is in the process of transitioning to the PostgreSQL DBMS, different instances of VMmanager may use different DMBS.
    The platform uses PostgreSQL in all new installations starting with version 2026.03.1. In all other cases, the platform uses MySQL. The DBMS is not changed when the platform is updated.
    To determine the type of DBMS, run the following command on the platform server:
    docker ps --filter name=pgsql
    Example answer
    CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 3213c5dc94d0 postgres:12 "docker-entrypoint.s…" 5 days ago Up 4 days 5432/tcp pgsql
    If the command output contains information about the container, the platform uses PostgreSQL; if the response is empty, it uses MySQL.
    PostgreSQL
```
docker exec -it pgsql bash -c "psql -d isp"
```
    MySQL
```
docker exec -it mysql bash -c "mysql isp -p\$MYSQL_ROOT_PASSWORD"
```
  3. Run the following query:
```
select state from vm_os where id = <id os>
```
    Comment:
    - <id os> — the ID of the OS that the image references.
    Example output
```
|state | deleted
```
    If the output shows deleted status, the issue is confirmed.

Solution

To resolve the issue, update the platform to version 2026.03.1 or later by following the instructions in the Update article.

Useful tips