OpenVZ Forum


Home » General » Support » Problem starting a copied container
Re: Problem starting a copied container [message #51088 is a reply to message #51087] Tue, 28 January 2014 01:29 Go to previous messageGo to previous message
wk38524 is currently offline  wk38524
Messages: 2
Registered: January 2014
Junior Member
Only thing that dmesg shows is:

[ 65.901793] CT: 201: started
[ 67.204622] CT: 201: stopped

I guess it's simfs since the filesystem shows as /dev/simfs

-----
Hardware node is CentOS 6.5
Kernel is 2.6.32-042stab084.17

vzctl-core-4.6.1-1.x86_64
vzstats-0.5.2-1.noarch
vzquota-3.1-1.x86_64
vzctl-4.6.1-1.x86_64
---
Original container
PHYSPAGES="0:51200"
DISKSPACE="1024000:1024000"
DISKINODES="50000:50000"
QUOTATIME="0"
CPUUNITS="1000"
HOSTNAME="vz200"
VE_ROOT="/vz/root/$VEID"
VE_PRIVATE="/vz/private/$VEID"
OSTEMPLATE="centos-6-x86-20131201"
ORIGIN_SAMPLE="basic"
IP_ADDRESS="192.168.0.200"
NAMESERVER="10.1.1.1"
SWAPPAGES="0"
CPULIMIT="10"
CPUS="1"
ONBOOT="yes"
---
Copied container
PHYSPAGES="0:51200"
DISKSPACE="1024000:1024000"
DISKINODES="50000:50000"
QUOTATIME="0"
CPUUNITS="1000"
HOSTNAME="vz201"
VE_ROOT="/vz/root/$VEID"
VE_PRIVATE="/vz/private/$VEID"
OSTEMPLATE="centos-6-x86-20131201"
ORIGIN_SAMPLE="basic"
IP_ADDRESS="192.168.0.201"
NAMESERVER="10.1.1.1"
SWAPPAGES="0"
CPULIMIT="10"
CPUS="1"
ONBOOT="no"

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: strange behaviour of the node
Next Topic: LVM checksum problem after yum update from CentOS 5.9 to CentOS 5.10 (w/o vzkernel update)
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu Jul 24 12:06:43 GMT 2025

Total time taken to generate the page: 0.46563 seconds
Powered by FUDforum Powered by Virtuozzo Containers