OpenVZ Forum - RDF feed
type: channel
items: Unable to start VM
items: Re: Unable to start VM

Unable to start VM
type: item
description: we tried restoring the vps from backup. All the files were restored without any problem but we getting error. vzctl start 190 Starting container ... Initializing quota ... Container is mounted Setting CPU limit: 400 Setting CPU units: 1000 Configure meminfo: 65536 Set hostname: localhost Unable to start init, probably incorrect template Container start failed Stopping container ... Container was stopped Container is unmounted Thanks
creator: whatever
date: 2009-08-13T16:34:40-00:00

Re: Unable to start VM
type: item
description: Hi, - Container sys architecure not supported, CT0 a i386; Container arch is amd64/x86_64 - Containter Template tree broken, init cannot be excute - you doesnt provide any info how the backup's are created, maybe restore path not correct, should /vz/private/<CTID> and not /vz/private/<CTID>/<PATH>/ - provide info about: # ls /vz/private/119/sbin/init # file /sbin/init # file /vz/private/119/sbin/init # grep OSTEMPLATE /etc/vz/conf/119.conf Bye, Thorsten
creator: curx
date: 2009-08-13T17:19:06-00:00

Re: Unable to start VM
type: item
description: /vz/private/190 and /etc/sysconfig/vz-scripts were backed and restored to the same location. Backup/restore done on the same machine. Below is the output [root@localhost private]# ls /vz/private/190/sbin/init /vz/private/190/sbin/init [root@localhost private]# file /sbin/init /sbin/init: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped [root@localhost private]# file /vz/private/190/sbin/init /vz/private/190/sbin/init: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped [root@localhost private]# grep OSTEMPLATE /etc/vz/conf/190.conf OSTEMPLATE="centos-5-i386-afull" [root@localhost private]# Thanks
creator: whatever
date: 2009-08-13T17:32:53-00:00

Re: Unable to start VM
type: item
description: Just to provide another alternative to this issue in case others come across it.... I requested a box, asked for x86_64, received x86_32 without realizing it. x86_32 VEs worked but x86_64 did not obviously. The error looked the same; after creation was complete the `vzctl start <VEID>` failed: lab1:/srv/vz # vzctl start 104 Starting container ... Container is mounted Adding IP address(es): 123.45.67.89 Setting CPU units: 1000 Configure meminfo: 65536 Set hostname: vebox204 Unable to start init, probably incorrect template Container start failed Stopping container ... Container was stopped Container is unmounted lab1:/srv/vz # echo $? 47 lab1:/srv/vz # Hopefully this saves some confusion in the future.
creator: dajoker
date: 2010-02-03T19:32:16-00:00