container not starting [message #37820] |
Sat, 24 October 2009 21:31 |
screenie
Messages: 6 Registered: October 2009
|
Junior Member |
|
|
hello,
i created an container from a template but i cannot start it;
openvz01:/# vzctl start 101
Starting container ...
Container is unmounted
Container is mounted
Setting CPU units: 1000
Setting CPUs: 1
Configure meminfo: 262144
Set hostname: test.domain.local
File resolv.conf was modified
Setting quota ugidlimit: 0
Container start in progress...
openvz01:/#
that's the entries from the syslog:
Oct 24 23:22:47 openvz01 kernel: [109450.070070] CT: 101: started
Oct 24 23:22:47 openvz01 kernel: [109450.331964] CT: 101: stopped
is there a method for detailed troubleshooting to figure out whats the problem?
i am running debian lenny with kernel 2.6.26-2-openvz-amd64, vz modules ar all loaded;
thx
[Updated on: Sun, 25 October 2009 00:11] Report message to a moderator
|
|
|
|
|
|
Re: container not starting [message #37984 is a reply to message #37962] |
Fri, 06 November 2009 20:07 |
screenie
Messages: 6 Registered: October 2009
|
Junior Member |
|
|
hello maratrus,
i am working in an large company and for virtualisation of linux machines, vmware, xen, or something is a waste of money and ressources;
the servers have two network interfaces, i bonded them together putted some vlans on it and attached a bridge interface to each of them;
as examle:
nic1\
=== bond0 == vmbr0 == CT101, CT102
nic2/ |_bond0.2 == vmbr1 == CT103, KVM1
|_bond0.3 == vmbr2 == CT104...8
|_bond0.4 == vmbr3 == KVM2, KVM5
|_bond0.5 == vmbr4 == CT109....15
|_....
proxmox v1.4 supports the networking part but our 1he servers have no hardware raid build in and only one pci-e extension slot which is in use;
changing the hardware is also not possible - we have a bunch of them and most of them are not one year old.....
so, we need md-devices but proxmox won't support software raid in their kernels and we don't want to setup this only on one single disk; a software raid1 has only advantages instead installing it on a single disk;
anyway, proxmox has the network options build in we need but software raid is also a must to have for us;
thx,
alex
[Updated on: Fri, 06 November 2009 20:14] Report message to a moderator
|
|
|
|
|
|
Re: container not starting [message #38087 is a reply to message #38083] |
Fri, 13 November 2009 22:10 |
ramjet
Messages: 16 Registered: September 2009
|
Junior Member |
|
|
Hi screenie,
I'm running 5 openvz servers. The first one deployed last year is a proxmox. It's still running version 1.1. Then I have a couple of Debian Lenny based 686 and amd64 ones I installed from scratch. I don't think you should mix the two. It's either proxmox with their choice of kernel or debian GNU/Linux lenny with their kernel.
proxmox:~# uname -a
Linux proxmox 2.6.24-2-pve #1 SMP PREEMPT Wed Jan 14 11:32:49 CET 2009 x86_64 GNU/Linux
proxmox:~# cat /proc/mdstat
cat: /proc/mdstat: No such file or directory
proxmox:~# modprobe md
proxmox:~# cat /proc/mdstat
Personalities :
unused devices: <none>
proxmox:~# modprobe raid10 raid0 raid456 raid1
proxmox:~# cat /proc/mdstat
Personalities : [raid10] [raid0] [raid6] [raid5] [raid4] [raid1]
unused devices: <none>
So apt-get install mdadm and figure out how to make proxmox use the software raid you setup.
Debian user since '96...
|
|
|