OpenVZ Forum


Home » General » Support » *SOLVED* Problem starting VPS
Re: Problem starting VPS [message #1839 is a reply to message #1838] Tue, 28 February 2006 11:37 Go to previous messageGo to previous message
dwebwarm is currently offline  dwebwarm
Messages: 11
Registered: February 2006
Location: Hewlett-Packard Global De...
Junior Member
Here the output of cat /proc/self/status

server2 ~ # cat /proc/self/status
Name:   cat
State:  R (running)
SleepAVG:       88%
Tgid:   10461
Pid:    10461
PPid:   2986
TracerPid:      0
Uid:    0       0       0       0
Gid:    0       0       0       0
FDSize: 256
Groups: 0 1 2 3 4 6 10 11 20 26 27
envID:  0
VPid:   10461
VmPeak:     1456 kB
VmSize:     1456 kB
VmLck:         0 kB
VmHWM:       360 kB
VmRSS:       360 kB
VmData:      144 kB
VmStk:        88 kB
VmExe:        16 kB
VmLib:      1180 kB
VmPTE:        12 kB
Threads:        1
SigQ:   0/12031
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000000000
SigCgt: 0000000000000000
CapInh: 0000000000000000
CapPrm: 00000000ffffffff
CapEff: 00000000fffffeff
TaskUB: 0
MMUB:   0


the odd thing here is, that I'm able to start VPS on onother node using P4 2.4 GHz CPU and SATA devices. I was able to start 5 different OS'es in a VPS too (Gentoo, CentoOS, Debian 3.1, Ubuntu 5.10 and Fedora Core 4). After using the same configuration here nothing happens Sad. It's a bit weird for me now. Maybe the problem is in the hardware and not software related. I mean, that OpenVZ is not working for me on Athlon/Sempron CPU arch, only on Intel based systems.
 
Read Message
Read Message
Read Message
Read Message
Read Message icon9.gif
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message icon14.gif
Read Message
Read Message icon14.gif
Previous Topic: Fully access to NIC
Next Topic: AutoFS/NFS
Goto Forum:
  


Current Time: Wed Sep 04 14:47:33 GMT 2024

Total time taken to generate the page: 0.05593 seconds