How to migrate VPSes from the old SolusVM master with OpenVZ 6 to the new SolusVM master with OpenVZ 7?
How to migrate OpenVZ VPS from other virtualization platform to SolusVM 2
SolusVM does not apply netmask set in IP block for OpenVZ VPSes
OpenVZ VPS is displayed as offline in SolusVM: Unable to connect to Virtuozzo. You may experience a connection problem or the server may be down. Contact your Virtuozzo administrator for assistance.
Unable to create a new OpenVZ VPS in SolusVM: create_prvt ERROR: Insufficient disk space
Migration from OpenVZ 6 to OpenVZ 7 via SolusVM web interface corrupts services inside VPS
Resource usage stats for a particular OpenVZ VPSes are displayed as 0 in SolusVM
Fail to create OpenVZ VPS with EZ template in SolusVM: Conflict: name 101 used as ctid
Attempt to reinstall OpenVZ 7 container fails: rootpassword is not provided
How to drop memory cache of OpenVZ VPS in SolusVM

See more

OpenVZ containers created through SolusVM using EZ templates do not boot : The hdd0 device does not exist

Updated March 30, 2022 05:53

Applicable to:

SolusVM

Symptoms

OpenVZ containers created through SolusVM using EZ templates do not boot.
Containers were created with disk index different from hdd0. The followiing error is generated in /usr/local/solusvm/log/ovz7.log on the corresponding OpenVZ node:

CONFIG_TEXT: /home/build/SOURCE/Go-Core/src/ovz7/main.go:127 main.main() failed 'prlctl set 101 --memsize 1048576000b --device-set hdd0 --size 21474836480b --swappages 0:0M' with stdErr: 'The hdd0 device does not exist. Failed to configure the virtual machine.

Cause

This is SolusVM bug with ID SVM-2871 which was fixed in SolusVM version 1.24.07.

Resolution

Update SolusVM to the latest mainline version.

Comments

0 comments

Please sign in to leave a comment.

Have more questions? Submit a request